about summary refs log tree commit diff
path: root/library/std/src/sync
diff options
context:
space:
mode:
authorKriskras99 <github@kriskras99.nl>2023-09-19 12:46:53 +0200
committerGitHub <noreply@github.com>2023-09-19 12:46:53 +0200
commitcdf25c904e7dc6eee089e1ccebc5fbd05351dfb9 (patch)
tree3505b520d9083bcbc6fd19f05135bfc1bef80b32 /library/std/src/sync
parentae9c330629f1fb03a636cb8af367fead024793db (diff)
downloadrust-cdf25c904e7dc6eee089e1ccebc5fbd05351dfb9.tar.gz
rust-cdf25c904e7dc6eee089e1ccebc5fbd05351dfb9.zip
Replace 'mutex' with 'lock' in RwLock documentation
When copying the documentation for `clear_poison` from Mutex, not every occurence of 'mutex' was replaced with 'lock'.
Diffstat (limited to 'library/std/src/sync')
-rw-r--r--library/std/src/sync/rwlock.rs4
1 files changed, 2 insertions, 2 deletions
diff --git a/library/std/src/sync/rwlock.rs b/library/std/src/sync/rwlock.rs
index 26aaa2414c9..ac7c800ff6f 100644
--- a/library/std/src/sync/rwlock.rs
+++ b/library/std/src/sync/rwlock.rs
@@ -380,7 +380,7 @@ impl<T: ?Sized> RwLock<T> {
     ///
     /// If the lock is poisoned, it will remain poisoned until this function is called. This allows
     /// recovering from a poisoned state and marking that it has recovered. For example, if the
-    /// value is overwritten by a known-good value, then the mutex can be marked as un-poisoned. Or
+    /// value is overwritten by a known-good value, then the lock can be marked as un-poisoned. Or
     /// possibly, the value could be inspected to determine if it is in a consistent state, and if
     /// so the poison is removed.
     ///
@@ -397,7 +397,7 @@ impl<T: ?Sized> RwLock<T> {
     ///
     /// let _ = thread::spawn(move || {
     ///     let _lock = c_lock.write().unwrap();
-    ///     panic!(); // the mutex gets poisoned
+    ///     panic!(); // the lock gets poisoned
     /// }).join();
     ///
     /// assert_eq!(lock.is_poisoned(), true);