From 6607982ab6cba2c778ce334987b8aa12a0b17150 Mon Sep 17 00:00:00 2001 From: Simon Sapin Date: Tue, 5 Mar 2019 10:07:35 +0100 Subject: [PATCH] =?UTF-8?q?liballoc:=20add=20unresolved=20=E2=80=9Csuperse?= =?UTF-8?q?t=20of=20core=3F=E2=80=9D=20question?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- text/0000-liballoc.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/text/0000-liballoc.md b/text/0000-liballoc.md index 05191bd614b..774c7185a77 100644 --- a/text/0000-liballoc.md +++ b/text/0000-liballoc.md @@ -323,4 +323,9 @@ It does provide a memory allocator through `malloc` and related functions, uncon In that sense it is closer to `std::io::prelude` than `std::prelude::v1`.~ Done in [PR #58933]. +* In addition to being a subset of `std`, should the `alloc` crate (by itself) + be a super-set of `core`? That is, should it reexport everything that is defined in `core`? + See [PR #58175] which proposes reexporting `core::sync::atomic` in `alloc::sync`. + [PR #58933]: https://github.com/rust-lang/rust/pull/58933 +[PR #58175]: https://github.com/rust-lang/rust/pull/58175