Tracking Issue for new_zeroed_alloc #129396
Description
Feature gate: #![feature(new_zeroed_alloc)]
Split-out from #63291 as a result of stabilizing most of its API! It's zeroed instead of uninit constructors, nothing too complicated!
Public API
It's new_zeroed and new_zeroed_slice on every major allocation type like Box, Rc, Arc.
impl<T> Box<T> { pub fn new_zeroed() -> Box<MaybeUninit<T>> {…} }
impl<T> Arc<T> { pub fn new_zeroed() -> Arc<MaybeUninit<T>> {…} }
impl<T> Rc<T> { pub fn new_zeroed() -> Rc<MaybeUninit<T>> {…} }
impl<[T]> Box<T> { pub fn new_zeroed_slice() -> Box<MaybeUninit<[T]>> {…} }
impl<[T]> Arc<T> { pub fn new_zeroed_slice() -> Arc<MaybeUninit<[T]>> {…} }
impl<[T]> Rc<T> { pub fn new_zeroed_slice() -> Rc<MaybeUninit<[T]>> {…} }Steps / History
- Implementation: #...
- added in alloc: Add new_zeroed() versions like new_uninit(). #66128
- other API was added in Tracking issue for uninitialized constructors for Box, Rc, Arc #63291
- Final comment period (FCP)1
- Stabilization PR
Unresolved Questions
- idk lol