Tracking Issue for `Box::as_non_null()`
Open
Nobody has claimed this yet.
A-box
A-raw-pointers
C-tracking-issue
S-tracking-needs-to-bake
T-libs
- Dominant language
- Rust
- Stars
- 119k
- Forks
- 16.1k
- PR merge metrics
- PR metrics pending
Description
Feature gate: #![feature(box_as_non_null)]
This is a tracking issue for Box::as_non_null()
See also #130364, #157843, and #129090 for similar features.
Public API
impl<T: ?Sized, A: Allocator> Box<T, A> {
pub fn as_non_null(b: &mut Self) -> NonNull<T>;
}
Steps / History
(Remember to update the S-tracking-* label when checking boxes.)
- ACP: rust-lang/libs-team#799
- Implementation: #157347
- Final comment period (FCP)^1
- Stabilization PR
Unresolved Questions
- Should this be named
as_non_nulloras_nonnull? See also https://github.com/rust-lang/rust/pull/157226#issuecomment-4608071258 - Confirm whether we want a
&selfor&mut selfargument. See also #157843.
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
Start by reading implementation PR #157347 and the related issues #130364, #157843, and #129090. Review the unresolved naming and receiver questions, then follow the feature lifecycle through FCP and a stabilization PR; done means those questions are resolved and stabilization is complete.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 20/100