We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Bump
I would argue that it is our best to name methods like in allocator_api feature (Box::allocator, Box::into_inner_with_allocator, etc.)
allocator_api
Box::allocator
Box::into_inner_with_allocator
The text was updated successfully, but these errors were encountered:
Not sure it is worth copying more of std here, rather than just waiting for the allocator API to stabilize.
std
Sorry, something went wrong.
This is mostly for ergonomics, for example to eliminate creation of arbitrary lifetimes for from_raw* functions.
from_raw*
No branches or pull requests
I would argue that it is our best to name methods like in
allocator_api
feature (Box::allocator
,Box::into_inner_with_allocator
, etc.)The text was updated successfully, but these errors were encountered: