wait_until
causes the current thread to block until the condition variable is notified, the given time point has been reached, or a spurious wakeup occurs. pred can be optionally provided to detect spurious wakeup.
1) Atomically calls lock.unlock() and blocks on *this.
The thread will be unblocked when
notify_all()or
notify_one()is executed, or
abs_timeis reached. It may also be unblocked spuriously.
When unblocked, calls lock.lock() (possibly blocking on the lock), then returns.
2)Equivalent to
while (!pred()).
This overload may be used to ignore spurious awakenings while waiting for a specific condition to become true.
Right after wait_until
returns, lock.owns_lock() is true, and lock.mutex() is locked by the calling thread. If these postconditions cannot be satisfied[1], calls std::terminate.
If any of the following conditions is satisfied, the behavior is undefined:
wait_until
) called on *this by those threads.Predicate
must meet the requirements of FunctionObject. -pred() must be a valid expression, and its type and value category must meet the BooleanTestable requirements. [edit] Return value
2) The latest result of pred() before returning to the caller.
[edit] Exceptions1) Timeout-related exceptions.
2) Timeout-related exceptions, and any exception thrown by pred.
[edit] NotesThe standard recommends that the clock tied to abs_time be used to measure time; that clock is not required to be a monotonic clock. There are no guarantees regarding the behavior of this function if the clock is adjusted discontinuously, but the existing implementations convert abs_time from Clock
to std::chrono::system_clock and delegate to POSIX pthread_cond_timedwait
so that the wait honors adjustments to the system clock, but not to the user-provided Clock
. In any case, the function also may wait for longer than until after abs_time has been reached due to scheduling or resource contention delays.
Even if the clock in use is std::chrono::steady_clock or another monotonic clock, a system clock adjustment may induce a spurious wakeup.
The effects of notify_one()
/notify_all()
and each of the three atomic parts of wait()
/wait_for()
/wait_until()
(unlock+wait, wakeup, and lock) take place in a single total order that can be viewed as modification order of an atomic variable: the order is specific to this individual condition variable. This makes it impossible for notify_one()
to, for example, be delayed and unblock a thread that started waiting just after the call to notify_one()
was made.
Possible output:
Waiting... Waiting... Waiting... Notifying... Notifying again... ...finished waiting. i == 1 ...finished waiting. i == 1 ...finished waiting. i == 1[edit] Defect reports
The following behavior-changing defect reports were applied retroactively to previously published C++ standards.
DR Applied to Behavior as published Correct behavior LWG 2093 C++11 timeout-related exceptions were missing in the specification mentions these exceptions LWG 2114RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4