From e9868ef8df9817802a0aaf0695e83c1e45783842 Mon Sep 17 00:00:00 2001 From: Ibraheem Ahmed Date: Tue, 11 Apr 2023 13:20:41 -0400 Subject: [PATCH] clarify wording around spurious wakeups from `thread::park` --- library/std/src/thread/mod.rs | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/library/std/src/thread/mod.rs b/library/std/src/thread/mod.rs index 07662e90c52..0f8b9c76688 100644 --- a/library/std/src/thread/mod.rs +++ b/library/std/src/thread/mod.rs @@ -891,8 +891,8 @@ pub fn sleep(dur: Duration) { /// performs the corresponding `Acquire` operation. Calls to `unpark` for the same /// thread form a [release sequence]. /// -/// Note that being unblocked does not imply synchronization with a call to `unpark`, -/// the wakeup could also be spurious. For example, a valid, but inefficient, +/// Note that being unblocked does not imply a call was made to `unpark`, because +/// wakeups can also be spurious. For example, a valid, but inefficient, /// implementation could have `park` and `unpark` return immediately without doing anything. /// /// # Examples