Struct Condvar
struct Condvar { ... }
A Condition Variable
For more information about condition variables, check out the documentation for the poisoning
variant of this type at poison::Condvar.
Examples
Note that this Condvar does not propagate information about threads that panic while
holding a lock. If you need this functionality, see poison::Mutex and poison::Condvar.
use ;
use Arc;
use thread;
let pair = new;
let pair2 = clone;
// Inside of our lock, spawn a new thread, and then wait for it to start.
spawn;
// Wait for the thread to start up.
let = &*pair;
let mut started = lock.lock;
while !*started
Implementations
impl Condvar
const fn new() -> CondvarCreates a new condition variable which is ready to be waited on and notified.
Examples
use Condvar; let condvar = new;fn wait<T>(self: &Self, guard: &mut MutexGuard<'_, T>)Blocks the current thread until this condition variable receives a notification.
This function will atomically unlock the mutex specified (represented by
guard) and block the current thread. This means that any calls tonotify_oneornotify_allwhich happen logically after the mutex is unlocked are candidates to wake this thread up. When this function call returns, the lock specified will have been re-acquired.Note that this function is susceptible to spurious wakeups. Condition variables normally have a boolean predicate associated with them, and the predicate must always be checked each time this function returns to protect against spurious wakeups.
Panics
This function may [
panic!] if it is used with more than one mutex over time.Examples
use ; use Arc; use thread; let pair = new; let pair2 = clone; spawn; // Wait for the thread to start up. let = &*pair; let mut started = lock.lock; // As long as the value inside the `Mutex<bool>` is `false`, we wait. while !*startedfn wait_while<T, F>(self: &Self, guard: &mut MutexGuard<'_, T>, condition: F) where F: FnMut(&mut T) -> boolBlocks the current thread until the provided condition becomes false.
conditionis checked immediately; if not met (returnstrue), this willwaitfor the next notification then check again. This repeats untilconditionreturnsfalse, in which case this function returns.This function will atomically unlock the mutex specified (represented by
guard) and block the current thread. This means that any calls tonotify_oneornotify_allwhich happen logically after the mutex is unlocked are candidates to wake this thread up. When this function call returns, the lock specified will have been re-acquired.Examples
use ; use Arc; use thread; let pair = new; let pair2 = clone; spawn; // Wait for the thread to start up. let = &*pair; // As long as the value inside the `Mutex<bool>` is `true`, we wait. let mut guard = lock.lock; cvar.wait_while;fn wait_timeout<T>(self: &Self, guard: &mut MutexGuard<'_, T>, dur: Duration) -> WaitTimeoutResultWaits on this condition variable for a notification, timing out after a specified duration.
The semantics of this function are equivalent to
waitexcept that the thread will be blocked for roughly no longer thandur. This method should not be used for precise timing due to anomalies such as preemption or platform differences that might not cause the maximum amount of time waited to be preciselydur.Note that the best effort is made to ensure that the time waited is measured with a monotonic clock, and not affected by the changes made to the system time. This function is susceptible to spurious wakeups. Condition variables normally have a boolean predicate associated with them, and the predicate must always be checked each time this function returns to protect against spurious wakeups. Furthermore, since the timeout is given relative to the moment this function is called, it needs to be adjusted when this function is called in a loop. The
wait_timeout_whilemethod lets you wait with a timeout while a predicate is true, taking care of all these concerns.The returned
WaitTimeoutResultvalue indicates if the timeout is known to have elapsed.Like
wait, the lock specified will have been re-acquired when this function returns, regardless of whether the timeout elapsed or not.Examples
use ; use Arc; use thread; use Duration; let pair = new; let pair2 = clone; spawn; // wait for the thread to start up let = &*pair; let mut started = lock.lock; // as long as the value inside the `Mutex<bool>` is `false`, we wait loopfn wait_timeout_while<T, F>(self: &Self, guard: &mut MutexGuard<'_, T>, dur: Duration, condition: F) -> WaitTimeoutResult where F: FnMut(&mut T) -> boolWaits on this condition variable for a notification, timing out after a specified duration.
The semantics of this function are equivalent to
wait_whileexcept that the thread will be blocked for roughly no longer thandur. This method should not be used for precise timing due to anomalies such as preemption or platform differences that might not cause the maximum amount of time waited to be preciselydur.Note that the best effort is made to ensure that the time waited is measured with a monotonic clock, and not affected by the changes made to the system time.
The returned
WaitTimeoutResultvalue indicates if the timeout is known to have elapsed without the condition being met.Like
wait_while, the lock specified will have been re-acquired when this function returns, regardless of whether the timeout elapsed or not.Examples
use ; use Arc; use thread; use Duration; let pair = new; let pair2 = clone; spawn; // wait for the thread to start up let = &*pair; let mut guard = lock.lock; let result = cvar.wait_timeout_while; if result.timed_out // access the locked mutex via guardfn notify_one(self: &Self)Wakes up one blocked thread on this condvar.
If there is a blocked thread on this condition variable, then it will be woken up from its call to
waitorwait_timeout. Calls tonotify_oneare not buffered in any way.To wake up all threads, see
notify_all.Examples
use ; use Arc; use thread; let pair = new; let pair2 = clone; spawn; // Wait for the thread to start up. let = &*pair; let mut started = lock.lock; // As long as the value inside the `Mutex<bool>` is `false`, we wait. while !*startedfn notify_all(self: &Self)Wakes up all blocked threads on this condvar.
This method will ensure that any current waiters on the condition variable are awoken. Calls to
notify_all()are not buffered in any way.To wake up only one thread, see
notify_one.Examples
use ; use Arc; use thread; let pair = new; let pair2 = clone; spawn; // Wait for the thread to start up. let = &*pair; let mut started = lock.lock; // As long as the value inside the `Mutex<bool>` is `false`, we wait. while !*started
impl Debug for Condvar
fn fmt(self: &Self, f: &mut Formatter<'_>) -> Result
impl Default for Condvar
fn default() -> CondvarCreates a
Condvarwhich is ready to be waited on and notified.
impl Freeze for Condvar
impl RefUnwindSafe for Condvar
impl Send for Condvar
impl Sync for Condvar
impl Unpin for Condvar
impl UnsafeUnpin for Condvar
impl UnwindSafe for Condvar
impl<T> Any for Condvar
fn type_id(self: &Self) -> TypeId
impl<T> Borrow for Condvar
fn borrow(self: &Self) -> &T
impl<T> BorrowMut for Condvar
fn borrow_mut(self: &mut Self) -> &mut T
impl<T> From for Condvar
fn from(t: T) -> TReturns the argument unchanged.
impl<T, U> Into for Condvar
fn into(self: Self) -> UCalls
U::from(self).That is, this conversion is whatever the implementation of
[From]<T> for Uchooses to do.
impl<T, U> TryFrom for Condvar
fn try_from(value: U) -> Result<T, <T as TryFrom<U>>::Error>
impl<T, U> TryInto for Condvar
fn try_into(self: Self) -> Result<U, <U as TryFrom<T>>::Error>