Created on 2022-02-09.00:00:00 last changed 12 months ago
Proposed resolution:
This wording is relative to N4901.
Modify [stdatomic.h.syn], header <stdatomic.h> synopsis, as indicated:
[Drafting Note: The editor is kindly requested to reorder these "atomic_fetch_KEY" declarations to match the other synopses in Clause [atomics]: add, sub, and, or, xor.]
[…] using std::atomic_fetch_or; // see below using std::atomic_fetch_or_explicit; // see below using std::atomic_fetch_xor; // see below using std::atomic_fetch_xor_explicit; // see below using std::atomic_fetch_and; // see below using std::atomic_fetch_and_explicit; // see below […]
[ 2022-07-25 Approved at July 2022 virtual plenary. Status changed: Ready → WP. ]
[ 2022-07-15; LWG telecon: move to Ready ]
[ 2022-03-04; Reflector poll ]
Set status to Tentatively Ready after eight votes in favour during reflector poll.
[ 2022-02-09; Jonathan comments and provides wording ]
C++20 [atomics.syn] has both of them, too, so it should definitely be in the common subset.
C17 subclause 7.17.7.5 provides atomic_fetch_xor and atomic_fetch_xor_explicit. stdatomic.h in the working draft (N4901) does not.
History | |||
---|---|---|---|
Date | User | Action | Args |
2023-11-22 15:47:43 | admin | set | status: wp -> c++23 |
2022-07-25 20:32:58 | admin | set | messages: + msg12638 |
2022-07-25 20:32:58 | admin | set | status: ready -> wp |
2022-07-25 20:28:19 | admin | set | messages: + msg12612 |
2022-03-04 14:33:21 | admin | set | messages: + msg12390 |
2022-03-04 14:33:21 | admin | set | status: new -> ready |
2022-02-10 16:06:13 | admin | set | messages: + msg12368 |
2022-02-10 16:06:13 | admin | set | messages: + msg12367 |
2022-02-09 00:00:00 | admin | create |