You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In addition to importing the contents of <stddef.h> into namespace std, the header also adds the typedef nullptr_t, and type byte, and operations on type byte. This additions are partially described in two different locations:
[cstddef.syn]p1 notes the addition of byte and its operations, but makes no mention of nullptr_t.
[diff.mods.to.declarations]p3 (in the C compatibility annex) notes the addition of nullptr_t, but says nothing about byte and its operations.
For consistency, we should either consolidate this descriptive material to either one place, or duplicate it completely in both. Opening and issue, rather than filing an initial PR, as not sure which direction would be preferred.
The text was updated successfully, but these errors were encountered:
As @jwakely noted in my attempted PR, modifying [depr.c.header.others] is a normative change that I'd like to discuss in an issue. I will open one if you don't mind.
PR #4145 contains a proposed change to [diff.mods.to.declarations], could you please take a look?
jensmaurer
changed the title
Inconsistent description of C++ extensions to header <cstddef>
Inconsistent description of C++ extensions to header <cstddef> LWG3484
May 13, 2022
In addition to importing the contents of <stddef.h> into namespace std, the header also adds the typedef nullptr_t, and type byte, and operations on type byte. This additions are partially described in two different locations:
[cstddef.syn]p1 notes the addition of byte and its operations, but makes no mention of nullptr_t.
[diff.mods.to.declarations]p3 (in the C compatibility annex) notes the addition of nullptr_t, but says nothing about byte and its operations.
For consistency, we should either consolidate this descriptive material to either one place, or duplicate it completely in both. Opening and issue, rather than filing an initial PR, as not sure which direction would be preferred.
The text was updated successfully, but these errors were encountered: