diff options
| author | bors <bors@rust-lang.org> | 2018-07-09 14:29:59 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2018-07-09 14:29:59 +0000 |
| commit | c6807bb1b282e0c5398aa4e659dbc165b6f3c81b (patch) | |
| tree | bf6777921022043285a1cb13f97b903b7ffbfdb2 /src/libstd/sys | |
| parent | c30acc7187fe5ab9ca8a34411bb89bfe241a0662 (diff) | |
| parent | 5b795cf57e42aa31da7cb175d8ff27633085b5d7 (diff) | |
| download | rust-c6807bb1b282e0c5398aa4e659dbc165b6f3c81b.tar.gz rust-c6807bb1b282e0c5398aa4e659dbc165b6f3c81b.zip | |
Auto merge of #52159 - SimonSapin:alloc-prelude, r=alexcrichton
Add the `alloc::prelude` module 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.
Diffstat (limited to 'src/libstd/sys')
0 files changed, 0 insertions, 0 deletions
