rust - https://github.com/rust-lang/rust

Age	Commit message (Collapse)	Author	Lines
2021-10-04	Auto merge of #89144 - sexxi-goose:insig_stdlib, r=nikomatsakis	bors	-0/+1
	2229: Mark insignificant dtor in stdlib I looked at all public [stdlib Drop implementations](https://doc.rust-lang.org/stable/std/ops/trait.Drop.html#implementors) and categorized them into Insigificant/Maybe/Significant Drop. Reasons are noted here: https://docs.google.com/spreadsheets/d/19edb9r5lo2UqMrCOVjV0fwcSdS-R7qvKNL76q7tO8VA/edit#gid=1838773501 One thing missing from this PR is tagging HashMap as insigificant destructor as that needs some discussion. r? `@Mark-Simulacrum` cc `@nikomatsakis`
2021-07-28	Remove redundant bounds on get_unchecked for vec_deque iterators, and run fmt	Frank Steffahn	-1/+3

2021-07-28	Add back TrustedRandomAccess-specialization for Vec, but only without coercions	Frank Steffahn	-1/+33

2021-07-28	Remove unsound TrustedRandomAccess implementations	Frank Steffahn	-30/+1
	Removes the implementations that depend on the user-definable trait `Copy`.
2021-06-16	Add doc(hidden) to all __iterator_get_unchecked	Jacob Hoffman-Andrews	-0/+1
	This method on the Iterator trait is doc(hidden), and about half of implementations were doc(hidden). This adds the attribute to the remaining implementations.
2021-05-16	mark internal inplace_iteration traits as hidden	The8472	-0/+2

2021-05-05	alloc: Add unstable Cfg feature `no-global_oom_handling`	John Ericson	-0/+2
	For certain sorts of systems, programming, it's deemed essential that all allocation failures be explicitly handled where they occur. For example, see Linus Torvald's opinion in [1]. Merely not calling global panic handlers, or always `try_reserving` first (for vectors), is not deemed good enough, because the mere presence of the global OOM handlers is burdens static analysis. One option for these projects to use rust would just be to skip `alloc`, rolling their own allocation abstractions. But this would, in my opinion be a real shame. `alloc` has a few `try_` methods already, and we could easily have more. Features like custom allocator support also demonstrate and existing to support diverse use-cases with the same abstractions. A natural way to add such a feature flag would a Cargo feature, but there are currently uncertainties around how std library crate's Cargo features may or not be stable, so to avoid any risk of stabilizing by mistake we are going with a more low-level "raw cfg" token, which cannot be interacted with via Cargo alone. Note also that since there is no notion of "default cfg tokens" outside of Cargo features, we have to invert the condition from `global_oom_handling` to to `not(no_global_oom_handling)`. This breaks the monotonicity that would be important for a Cargo feature (i.e. turning on more features should never break compatibility), but it doesn't matter for raw cfg tokens which are not intended to be "constraint solved" by Cargo or anything else. To support this use-case we create a new feature, "global-oom-handling", on by default, and put the global OOM handler infra and everything else it that depends on it behind it. By default, nothing is changed, but users concerned about global handling can make sure it is disabled, and be confident that all OOM handling is local and explicit. For this first iteration, non-flat collections are outright disabled. `Vec` and `String` don't yet have `try_` allocation methods, but are kept anyways since they can be oom-safely created "from parts", and we hope to add those `try_` methods in the future. [1]: https://lore.kernel.org/lkml/CAHk-=wh_sNLoz84AUUzuqXEsYH35u=8HV3vK-jbRbJ_B-JjGrg@mail.gmail.com/
2021-03-29	fix double-drop in in-place collect specialization	The8472	-9/+18

2021-02-15	Turn may_have_side_effect into an associated constant	Tomasz Miąsko	-3/+1
	The `may_have_side_effect` is an implementation detail of `TrustedRandomAccess` trait. It describes if obtaining an iterator element may have side effects. It is currently implemented as an associated function. Turn `may_have_side_effect` into an associated constant. This makes the value immediately available to the optimizer.
2020-12-30	Fix rustdoc link in vec/into_iter.rs.	Mara Bos	-2/+2

2020-12-29	docs: fixing references	C	-1/+1

2020-12-29	style: applying Rust style	C	-9/+7

2020-12-29	refactor: moving AsIntoIter into into_iter.rs	C	-0/+15

2020-12-29	refactor: moved IntoIter into into_iter.rs	C	-0/+270