Tracking Issue for `AtomicPtr::null`
Open
Nobody has claimed this yet.
C-tracking-issue
T-libs
- Dominant language
- Rust
- Stars
- 119k
- Forks
- 16.1k
- PR merge metrics
- PR metrics pending
Description
Feature gate: #![feature(atomic_ptr_null)]
This is a tracking issue for the constructor of a null atomic pointer.
Public API
impl<T> AtomicPtr<T> {
pub const fn null() -> Self {
Self::new(core::ptr::null_mut())
}
}
Steps / History
(Remember to update the S-tracking-* label when checking boxes.)
- ACP: https://github.com/rust-lang/libs-team/issues/715
- Implementation: https://github.com/rust-lang/rust/pull/150736
- 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
Start by reviewing the atomic_ptr_null feature gate, the public AtomicPtr::null API shown in the issue, and implementation PR #150736. The remaining work is to follow the feature lifecycle through the final comment period and stabilization PR; done means the listed stabilization steps are completed with no unresolved questions.
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
- Mostly clear
- Newbie friendliness
- 25/100