Tracking Issue for `lock_value_accessors`

Feature gate: #![feature(lock_value_accessors)]

This is a tracking issue for feature lock_value_accessors.

Public API

impl<T> Mutex<T> {
    pub fn get_cloned(&self) -> Result<T, PoisonError<()>> where T: Clone { ... }
    pub fn set(&self, value: T) -> Result<(), PoisonError<T>> { ... }
    pub fn replace(&self, value: T) -> LockResult<T> { ... }
}

impl<T> RwLock<T> {
    pub fn get_cloned(&self) -> Result<T, PoisonError<()>> where T: Clone { ... }
    pub fn set(&self, value: T) -> Result<(), PoisonError<T>> { ... }
    pub fn replace(&self, value: T) -> LockResult<T> { ... }
}

impl<T> nonpoison::Mutex<T>
where
    T: ?Sized
{
    pub fn get_cloned(&self) -> T where T: Clone { ... }
    pub fn set(&self, value: T) { ... }
    pub fn replace(&self, value: T) -> T { ... }
    pub fn with_mut<F, R>(&self, f: F) -> R where F: FnOnce(&mut T) -> R { ... }
}

impl<T> nonpoison::RwLock<T>
where
    T: ?Sized
{
    pub fn get_cloned(&self) -> T where T: Clone { ... }
    pub fn set(&self, value: T) { ... }
    pub fn replace(&self, value: T) -> T { ... }
    pub fn with<F, R>(&self, f: F) -> R where F: FnOnce(&T) -> R { ... }
    pub fn with_mut<F, R>(&self, f: F) -> R where F: FnOnce(&mut T) -> R { ... }
}

Steps / History

• ACP: https://github.com/rust-lang/libs-team/issues/485
• Implementation: #133406
• Implementation: #147328
• Final comment period (FCP)^1
• Stabilization PR

Unresolved Questions

• Whether we should checking poisoning first and avoid unnecessary lock acquire attempts.

Links

• Follow-up ACP: https://github.com/rust-lang/libs-team/issues/497

Start with the public API and the completed implementation links, #133406 and #147328, then read ACPs 485 and 497 and the stabilization guide. The remaining work is the final comment period and stabilization PR; resolve the open poisoning question before considering the feature ready.