-
Notifications
You must be signed in to change notification settings - Fork 12.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix out of date unstable book entries for alloc_*
features.
#45217
Conversation
Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @steveklabnik (or someone else) soon. If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes. Please see the contribution instructions for more information. |
@@ -14,7 +14,7 @@ | |||
#![unstable(feature = "alloc_system", | |||
reason = "this library is unlikely to be stabilized in its current \ | |||
form or name", | |||
issue = "27783")] | |||
issue = "32838")] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nice catch
@bors: r+ rollup thanks! This is great. |
📌 Commit 818d224 has been approved by |
Fix out of date unstable book entries for `alloc_*` features. The `alloc_jemalloc` crate does not provide a type to use with `#[global_allocator]`, and (according to Alex) `extern crate alloc_jemalloc;` alone became a no-op when `#[global_allocator]` was introduced.
The
alloc_jemalloc
crate does not provide a type to use with#[global_allocator]
, and (according to Alex)extern crate alloc_jemalloc;
alone became a no-op when#[global_allocator]
was introduced.