Tracking Issue for Unlockable Guards

[SpaceBroetchen]

Feature gate: #![feature(unlockable_guards)]

This is a tracking issue for unlocking nonpoison guards temporary while only holding a mutable reference to them.

Public API

// std::sync::nonpoison::mutex

#[unstable(feature = "unlockable_guards", issue = "148568")]
#[unstable(feature = "nonpoison_mutex", issue = "134645")]
impl<T: ?Sized> MutexGuard<'_, T> {
    pub fn unlocked<F>(self: &mut Self, func: F) where F: FnOnce() -> ();
}

// std::sync::nonpoison::rwlock

#[unstable(feature = "unlockable_guards", issue = "148568")]
#[unstable(feature = "nonpoison_mutex", issue = "134645")]
impl<T: ?Sized> RwLockWriteGuard<'_, T> {
    pub fn unlocked<F>(self: &mut Self, func: F) where F: FnOnce() -> ();
}

#[unstable(feature = "unlockable_guards", issue = "148568")]
#[unstable(feature = "nonpoison_mutex", issue = "134645")]
impl<T: ?Sized> RwLockReadGuard<'_, T> {
    pub fn unlocked<F>(self: &mut Self, func: F) where F: FnOnce() -> ();
}

Steps / History

• ACP: ACP: Freezable Mutex Guards libs-team#679
• Implementation: #...
• Final comment period (FCP)¹
• Stabilization PR

Unresolved Questions

• None yet.

Footnotes

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

[joboet]

These should not be methods in order to avoid conflicting with methods from the inner types accessible via dereferencing (naming the first parameter self is probably an oversight).