about summary refs log tree commit diff
path: root/src/libstd/thread
diff options
context:
space:
mode:
authorRalf Jung <post@ralfj.de>2018-12-03 15:14:31 +0100
committerRalf Jung <post@ralfj.de>2018-12-03 15:14:31 +0100
commit76cd8f05945e5edd8272e2e8c8f41ffd0182f403 (patch)
tree7f8f49408e6d0f1b1ab5c2fe84be65216e0592ff /src/libstd/thread
parent7b6ad7a960dd330e8c8401a598bd2f2ec6901100 (diff)
downloadrust-76cd8f05945e5edd8272e2e8c8f41ffd0182f403.tar.gz
rust-76cd8f05945e5edd8272e2e8c8f41ffd0182f403.zip
improve wording
Diffstat (limited to 'src/libstd/thread')
-rw-r--r--src/libstd/thread/mod.rs7
1 files changed, 4 insertions, 3 deletions
diff --git a/src/libstd/thread/mod.rs b/src/libstd/thread/mod.rs
index 4a5ba9b800e..68d3f19cdea 100644
--- a/src/libstd/thread/mod.rs
+++ b/src/libstd/thread/mod.rs
@@ -806,9 +806,10 @@ const NOTIFIED: usize = 2;
 /// In other words, each [`Thread`] acts a bit like a spinlock that can be
 /// locked and unlocked using `park` and `unpark`.
 ///
-/// Notice that it would be a valid (but inefficient) implementation to make both [`park`] and
-/// [`unpark`] NOPs that return immediately.  Being unblocked does not imply
-/// any synchronization with someone that unparked this thread, it could also be spurious.
+/// Notice that being unblocked does not imply any synchronization with someone
+/// that unparked this thread, it could also be spurious.
+/// For example, it would be a valid, but inefficient, implementation to make both [`park`] and
+/// [`unpark`] return immediately without doing anything.
 ///
 /// The API is typically used by acquiring a handle to the current thread,
 /// placing that handle in a shared data structure so that other threads can