Tracking Issue for `cast_maybe_uninit`
Open
Nobody has claimed this yet.
C-tracking-issue
S-tracking-unimplemented
T-libs
- Dominant language
- Rust
- Stars
- 119k
- Forks
- 16.1k
- PR merge metrics
- PR metrics pending
Description
Feature gate: #![feature(cast_maybe_uninit)]
This is a tracking issue for the cast_init and cast_uninit methods on pointers.
Public API
impl<T> *const T {
pub const fn cast_uninit(self) -> *const MaybeUninit<T>;
}
impl<T> *mut T {
pub const fn cast_uninit(self) -> *mut MaybeUninit<T>;
}
impl<T> NonNull<T> {
pub const fn cast_uninit(self) -> NonNull<MaybeUninit<T>>;
}
impl<T> *const MaybeUninit<T> {
pub const fn cast_init(self) -> *const T;
}
impl<T> *mut MaybeUninit<T> {
pub const fn cast_init(self) -> *mut T;
}
impl<T> NonNull<MaybeUninit<T>> {
pub const fn cast_init(self) -> NonNull<T>;
}
Steps / History
(Remember to update the S-tracking-* label when checking boxes.)
- ACP: rust-lang/libs-team#627
- Implementation: #145325
- Final comment period (FCP)^1
- Stabilization PR
Unresolved Questions
- None yet.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review implementation PR #145325 and the stabilization guide linked in the issue first. The remaining work shown is the final comment period and stabilization PR; done means those unchecked lifecycle steps are completed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100