This is a tracking issue for the RFC "Deprecate uninitialized
in favor of a new MaybeUninit
type" (rust-lang/rfcs#1892).
Most of this has been stabilized, this issue now only tracks the below unstable methods.
Public APIimpl<T> [MaybeUninit<T>] { pub unsafe fn assume_init_drop(&mut self); pub const unsafe fn assume_init_ref(&self) -> &[T]; pub const unsafe fn assume_init_mut(&mut self) -> &mut [T]; pub const fn slice_as_ptr(this: &[MaybeUninit<T>]) -> *const T; pub const fn slice_as_mut_ptr(this: &mut [MaybeUninit<T>]) -> *mut T; }Steps / History
slice_as_ptr
/slice_as_mut_ptr
be methods (with some Self
parameter) instead of functions?slice_as_ptr
/slice_as_mut_ptr
get rid of the slice length, so .add(n)
needs to be used on the result instead of a safer [n]
. See accepted ACP Remove MaybeUninit::slice_as_(mut_)ptr
and optionally add *const/*mut MaybeUninit<T> -> *const/*mut T
type safe conversions libs-team#245 and its incomplete implementation Nuke slice_as{,_mut}_ptr methods of MaybeUninit #103133stanislav-tkach, coffeenotfound, paolobarbolini, YangKeao, kornelski and 10 more
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4