5 Simple Techniques For sleep
5 Simple Techniques For sleep
Blog Article
atomic_compare_exchange_weakatomic_compare_exchange_weak_explicitatomic_compare_exchange_strongatomic_compare_exchange_strong_explicit
atomic_compare_exchange_weakatomic_compare_exchange_weak_explicitatomic_compare_exchange_strongatomic_compare_exchange_strong_explicit
If policy is std::launch::async
remaining - pointer to the object to put the remaining time on interruption. Could possibly be NULL, by which circumstance it really is disregarded
Even when the shared variable is atomic, it have to be modified though owning the mutex to correctly publish the modification towards the ready thread.
The very best-stage functionality may possibly connect its return value or an exception to the caller via std::assure or by modifying shared variables (which can require synchronization, see std::mutex and std::atomic).
Regardless of whether the clock in use is std::chrono::steady_clock or One more monotonic clock, a program clock adjustment may perhaps induce a spurious wakeup.
Although notified under lock, overload (one) will make no guarantees with regards to the condition of the associated predicate when returning as a consequence of Stages of sleep timeout.
In almost any scenario, the functionality also may possibly watch for more time than until eventually right after abs_time has become attained on account of scheduling or useful resource rivalry delays.
This perform might block for for a longer time than sleep_duration on account of scheduling or useful resource rivalry delays.
length and remaining may possibly issue at a similar item, which simplifies re-managing the perform after a signal.
std::launch::deferred.
atomic_compare_exchange_weakatomic_compare_exchange_weak_explicitatomic_compare_exchange_strongatomic_compare_exchange_strong_explicit
atomic_compare_exchange_weakatomic_compare_exchange_weak_explicitatomic_compare_exchange_strongatomic_compare_exchange_strong_explicit
std::condition_variable is often a synchronization primitive made use of which has a std::mutex to dam one or more threads right up until A further thread both modifies a shared variable (the condition) and notifies the std::condition_variable.