Tracking Issue for `const_nonnull_with_exposed_provenance`
Open
Nobody has claimed this yet.
C-tracking-issue
S-tracking-unimplemented
T-libs
- Dominant language
- Rust
- Stars
- 119k
- Forks
- 16.2k
- PR merge metrics
- PR metrics pending
Description
Feature gate: #![feature(const_nonnull_with_exposed_provenance)]
This is a tracking issue for marking NonNull::with_exposed_provenance const.
Public API
// Before
pub fn with_exposed_provenance(addr: NonZero<usize>) -> Self;
// After
pub const fn with_exposed_provenance(addr: NonZero<usize>) -> Self;
Steps / History
- Mark
NonNull::with_exposed_provenanceas const.
(Remember to update the S-tracking-* label when checking boxes.)
- ACP: rust-lang/libs-team#763
- Implementation: #154216
- 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
The tracking issue concerns making NonNull::with_exposed_provenance const; its implementation is already linked as PR #154216. Read the linked implementation and the feature lifecycle guidance, then check the remaining FCP and stabilization steps rather than starting a new implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- compilers
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 20/100