Tracking Issue for `unsafe_cell_access`

[pitaj]

Feature gate: #![feature(unsafe_cell_access)]

This is a tracking issue for direct access APIs on UnsafeCell (without going through raw pointers).

Public API

// core::cell

impl<T> UnsafeCell<T> {
    pub unsafe fn replace(&self, new_value: T) -> T;
}
impl<T: ?Sized> UnsafeCell<T> {
    pub unsafe fn as_ref_unchecked(&self) -> &T;
    pub unsafe fn as_mut_unchecked(&self) -> &mut T;
}

Steps / History

• ACP: UnsafeCell access APIs libs-team#521
• Implementation: add UnsafeCell direct access APIs #136398
• Final comment period (FCP)¹
• Stabilization PR

Unresolved Questions

• None yet.

Footnotes

1. https://std-dev-guide.rust-lang.org/feature-lifecycle/stabilization.html ↩

[nazar-pc]

Is there something else needed before FCP can start here? The implementation is straightforward, but it uses #122034 internally, not sure if there is a correlation between the two.

[pitaj]

I think we typically want to allow some time for the feature to be used before stabilizing it.