Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://github.com/rust-lang/rust/issues/96097 below:

Tracking Issue for MaybeUninit methods for arrays · Issue #96097 · rust-lang/rust · GitHub

This is a meta-tracking issue for multiple APIs that are linked across multiple issues. Right now it only includes two methods, but since there seems to be a desire to add more, this issue can be used as a placeholder for those discussions until those methods are added.

impl<T> MaybeUninit<T> {
    pub const fn array_assume_init<const N: usize>(array: [Self; N]) -> [T; N];
}

impl<T, const N: usize> MaybeUninit<[T; N]> {
    pub const fn transpose(self) -> [MaybeUninit<T>; N];
}

impl<T, const N: usize> [MaybeUninit<T>; N] {
    pub const fn transpose(self) -> MaybeUninit<[T; N]>;
}

• Add MaybeUninit methods uninit_array, slice_get_ref, slice_get_mut #65580
• Add MaybeUninit method array_assume_init #80600
• Make const: MaybeUninit array cleanup #96099
• Add MaybeUninit array transpose impls #102023
• Replace uses of MaybeUninit::uninit_array() with inline const blocks. #125082
• Final comment period (FCP)
• Stabilization PR

• Old tracking issue for array_assume_init: Tracking Issue for maybe_uninit_array_assume_init #80908

• Should MaybeUninit::uninit_array::<LEN>() be stabilised if it can be replaced by [const { MaybeUninit::uninit() }; LEN] ?
  • No, fcp close to remove that: Tracking Issue for MaybeUninit methods for arrays #96097 (comment)
• What other APIs should be added for arrays?
• Is array_assume_init the right pattern, or should we convert from [MaybeUninit<T>, N] back to MaybeUninit<[T; N]> first?

elichai, TimLuq, briansmith, smasher164, orzogc and 14 moreelichai, Paval-from-Belarus, botahamec, bjoernager, JulianSchmid and 2 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