USA Today: Atomic Habits: An Easy & Proven Way to Build Good Habits & Break Bad Ones
The #1 New York Times bestseller. Over 10 million copies sold! Tiny Changes, Remarkable Results No matter your goals, Atomic Habits offers a proven framework for improving--every day. James Clear, one ...
Atomic Habits: An Easy & Proven Way to Build Good Habits & Break Bad Ones
C++ includes built-in support for threads, atomic operations, mutual exclusion, condition variables, and futures.
Each instantiation and full specialization of the std::atomic template defines an atomic type. If one thread writes to an atomic object while another thread reads from it, the behavior is well-defined (see memory model for details on data races). In addition, accesses to atomic objects may establish inter-thread synchronization and order non-atomic memory accesses as specified by std::memory ...
Each atomic object has its own associated modification order, which is a total order of modifications made to that object. If, from some thread's point of view, modification A of some atomic M happens-before modification B of the same atomic M, then in the modification order of M, A occurs before B.
Atomically replaces the current value with desired. Memory is affected according to the value of order.
On success, the operation is an atomic read-modify-write operation on *this and expected is not accessed after the atomic update. On failure, the operation is an atomic load operation on *this and expected is updated with the existing value read from the atomic object.
atomic_compare_exchange_weak_explicit may fail spuriously. If expected is a null pointer, or failure is std::memory_order_release or std::memory_order_acq_rel, the behavior is undefined. If p is a null pointer, the behaviors of these functions are all undefined.