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

Age	Commit message (Collapse)	Author	Lines
2019-03-05	Move alloc::prelude::* to alloc::prelude::v1, make alloc a subset of std	Simon Sapin	-19/+0
	This was one of the unresolved questions of https://github.com/rust-lang/rfcs/pull/2480. As the RFC says this is maybe not useful in the sense that we are unlikely to ever have a second version, but making the crate a true subset makes one less issue to think about if we stabilize it and later want to merge standard library crates and have Cargo feature flags to enable or disable parts of the `std` crate. See also discussion in https://github.com/rust-lang/rust/pull/58175
2019-02-03	liballoc: revert nested imports style changes.	Mazdak Farrokhzad	-8/+5

2019-02-02	liballoc: refactor & fix some imports.	Mazdak Farrokhzad	-5/+8

2019-02-02	liballoc: cargo check passes on 2018	Mazdak Farrokhzad	-5/+5

2018-12-25	Remove licenses	Mark Rousskov	-10/+0

2018-07-07	Add the `alloc::prelude` module	Simon Sapin	-0/+29
	It contains the re-exports that are in `std::prelude::v1` but not in `core::prelude::v1`. Calling it prelude is somewhat of a misnomer since (unlike those modules in `std` or `core`) its contents are never implicitly imported in modules. Rather it is intended to be used with an explicit glob import like `use alloc::prelude::*;`. However there is precedent for the same misnomer with `std::io::prelude`, for example. This new module is unstable with the same feature name as the `alloc` care. They are proposed for stabilization together in RFC https://github.com/rust-lang/rfcs/pull/2480