This page is a snapshot from the LWG issues list, see the Library Active Issues List for more information and the meaning of New status.
Section: 32.5.6 [atomics.wait] Status: New Submitter: Jonathan Wakely Opened: 2026-07-17 Last modified: 2026-07-17
Priority: Not Prioritized
View other active issues in [atomics.wait].
View all other issues in [atomics.wait].
View all issues with New status.
Discussion:
When LEWG looked at issue 3417(i) in Brno, it was suggested that instead of just deprecating (and then removing via P2866) non-lock-free wait/notify on volatile atomics, we should remove all wait/notify on volatile atomics. If the value of a volatile atomic object changes spontaneously (as volatile objects are wont to do) then threads blocked waiting for it to change will not be notified. This makes using wait/notify on volatile objects unreliable and of questionable value.
Proposed resolution: