mirror of
https://github.com/rust-lang/rust.git
synced 2024-11-22 23:04:33 +00:00
Rollup merge of #121736 - HTGAzureX1212:HTGAzureX1212/remove-mutex-unlock, r=jhpratt
Remove `Mutex::unlock` Function As of the completion of the FCP in https://github.com/rust-lang/rust/issues/81872#issuecomment-1474104525, it has come to the conclusion to be closed. This PR removes the function entirely in light of the above. Closes #81872.
This commit is contained in:
commit
90ca049320
@ -369,26 +369,6 @@ impl<T: ?Sized> Mutex<T> {
|
||||
}
|
||||
}
|
||||
|
||||
/// Immediately drops the guard, and consequently unlocks the mutex.
|
||||
///
|
||||
/// This function is equivalent to calling [`drop`] on the guard but is more self-documenting.
|
||||
/// Alternately, the guard will be automatically dropped when it goes out of scope.
|
||||
///
|
||||
/// ```
|
||||
/// #![feature(mutex_unlock)]
|
||||
///
|
||||
/// use std::sync::Mutex;
|
||||
/// let mutex = Mutex::new(0);
|
||||
///
|
||||
/// let mut guard = mutex.lock().unwrap();
|
||||
/// *guard += 20;
|
||||
/// Mutex::unlock(guard);
|
||||
/// ```
|
||||
#[unstable(feature = "mutex_unlock", issue = "81872")]
|
||||
pub fn unlock(guard: MutexGuard<'_, T>) {
|
||||
drop(guard);
|
||||
}
|
||||
|
||||
/// Determines whether the mutex is poisoned.
|
||||
///
|
||||
/// If another thread is active, the mutex can still become poisoned at any
|
||||
|
Loading…
Reference in New Issue
Block a user