Tracking issue for #![feature(maybe_uninit_slice)] · Issue #63569 · rust-lang/rust (original) (raw)

Skip to content

Navigation Menu

• • GitHub Copilot Write better code with AI
  • GitHub Advanced Security Find and fix vulnerabilities
  • Actions Automate any workflow
  • Codespaces Instant dev environments
  • Issues Plan and track work
  • Code Review Manage code changes
  • Discussions Collaborate outside of code
  • Code Search Find more, search less
• Explore
  • Learning Pathways
  • Events & Webinars
  • Ebooks & Whitepapers
  • Customer Stories
  • Partners
  • Executive Insights
• • GitHub Sponsors Fund open source developers
  • The ReadME Project GitHub community articles
• • Enterprise platform AI-powered developer platform
• Pricing

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Sign up

Description

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 API

impl [MaybeUninit] { 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

• Implementation
• Make slice methods inherent: Add inherent versions of MaybeUninit methods for slices #129259
• Ensure documentation has examples
• Final comment period (FCP)
• Stabilization PR

Unresolved Questions

• Should slice_as_ptr/slice_as_mut_ptr be methods (with some Self parameter) instead of functions?