This page is a snapshot from the LWG issues list, see the Library Active Issues List for more information and the meaning of NAD status.
Section: 29 [atomics] Status: NAD Submitter: BSI Opened: 2010-08-25 Last modified: 2017-02-03
Priority: Not Prioritized
View all other issues in [atomics].
View all issues with NAD status.
Table 143 lists the typedefs for various atomic types corresponding to the various standard integer typedefs, such as atomic_int_least8_t for int_least8_t, and atomic_uint_fast64_t for uint_fast64_t. However, there are no atomic typedefs corresponding to the fixed-size standard typedefs int8_t, int16_t, and so forth.
[ 2010-10-24 Daniel adds: ]
Accepting n3164 would solve this issue.
[ 2011-02-15 Anthony corrects numbering/naming for N3225, Howard suggests improvement for the position of '(optional)', Daniel reorders rows in harmony to remaining entries and suggests specific optionality comments: ]
[2011-02-16 Reflector discussion]
Moved to Tentatively Ready after 5 votes.
[2011-03-16: Hans reopenes and comments]
WG14 briefly discussed LWG 1456. It turns out that they had previously made a conscious decision not to make a similar change. If C++ would deviate, this would introduce a C divergence.We should reopen the issue and, in my opinion, probably resolve it as NAD instead. This is in a part of the standard that is there mostly for C compatibility, so introducing divergence here seems to make no sense.
WG14 does not require these typedefs, and we see no reason to be gratuitously different.
Add the following entries to table 143:
Table 146 — atomic <inttypes.h> typedefs Atomic typedef <inttypes.h> type ... ... atomic_intmax_t intmax_t atomic_uintmax_t uintmax_t