about summary refs log tree commit diff
diff options
context:
space:
mode:
authorDylan DPC <99973273+Dylan-DPC@users.noreply.github.com>2022-06-07 17:25:44 +0200
committerGitHub <noreply@github.com>2022-06-07 17:25:44 +0200
commitf12605b9ef252aadcba004485796116debefd2ae (patch)
tree592a8a484705f80bd559bebca3c15963891bd119
parent32d945d9bd4aa4c0c381a5112d5acf39dccf6a33 (diff)
parente224185409bd20b91c5eb0652748283658d7c4dd (diff)
downloadrust-f12605b9ef252aadcba004485796116debefd2ae.tar.gz
rust-f12605b9ef252aadcba004485796116debefd2ae.zip
Rollup merge of #97821 - Nilstrieb:mutex-docs, r=Dylan-DPC
Remove confusing sentence from `Mutex` docs

The docs were saying something about "statically initializing" the
mutex, and it's not clear what this means. Remove that part to avoid
confusion.
-rw-r--r--library/std/src/sync/mutex.rs9
1 files changed, 4 insertions, 5 deletions
diff --git a/library/std/src/sync/mutex.rs b/library/std/src/sync/mutex.rs
index 3d8281fe593..b2fbb77204a 100644
--- a/library/std/src/sync/mutex.rs
+++ b/library/std/src/sync/mutex.rs
@@ -10,11 +10,10 @@ use crate::sys_common::mutex as sys;
 /// A mutual exclusion primitive useful for protecting shared data
 ///
 /// This mutex will block threads waiting for the lock to become available. The
-/// mutex can also be statically initialized or created via a [`new`]
-/// constructor. Each mutex has a type parameter which represents the data that
-/// it is protecting. The data can only be accessed through the RAII guards
-/// returned from [`lock`] and [`try_lock`], which guarantees that the data is only
-/// ever accessed when the mutex is locked.
+/// mutex can be created via a [`new`] constructor. Each mutex has a type parameter
+/// which represents the data that it is protecting. The data can only be accessed
+/// through the RAII guards returned from [`lock`] and [`try_lock`], which
+/// guarantees that the data is only ever accessed when the mutex is locked.
 ///
 /// # Poisoning
 ///