The Definitive Guide to sleep
The Definitive Guide to sleep
Blog Article
The returned price of overload (three) suggests no matter whether pred evaluated to legitimate, regardless of whether there was a stop asked for or not.
atomic_compare_exchange_weakatomic_compare_exchange_weak_explicitatomic_compare_exchange_strongatomic_compare_exchange_strong_explicit
If coverage is std::launch::async
remaining - pointer to the article to put the remaining time on interruption. May very well be NULL, through which case it truly is ignored
Mutual exclusion algorithms avert multiple threads from concurrently accessing shared methods. This helps prevent information races and supplies aid for synchronization among threads. Outlined in header
Waits for the result to become readily available. Blocks until specified timeout_duration has elapsed or the result gets out there, whichever comes 1st. The return benefit identifies the point out of the result.
Even when the clock in use is std::chrono::steady_clock or Yet another monotonic clock, a technique clock adjustment may possibly induce a spurious wakeup.
Frequent Rationalization future_status::deferred The shared point How sleep cycle works out has a deferred functionality applying lazy evaluation, so the result is going to be computed only when explicitly asked for future_status::Completely ready The end result is prepared future_status::timeout The timeout has expired [edit] Exceptions
This overload could possibly be employed to ignore spurious awakenings though watching for a certain problem to become legitimate.
This function may well block for for a longer time than sleep_duration due to scheduling or useful resource competition delays.
period and remaining might issue at the identical item, which simplifies re-managing the function following a signal.
std::start::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
Should the functionality file returns a worth or throws an exception, it is stored in the shared state accessible through the std::future that std::async returns towards the caller. [edit] Deferred invocation