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
The note in [atomics.types.operations] p23 says "if the underlying type has ..." but this is not the same meaning of "underlying type" used elsewhere ([basic.fundamental] and [dcl.enum]).
[atomics.types.generic] uses the phrase "the template argument for T", and the nested type value_type is also defined. Either would be better than "the underlying type", but I think the note would be improved by referring to "object representation of the type", possibly even making use of std::has_unique_object_representations.
The text was updated successfully, but these errors were encountered:
std::has_unique_object_representations is probably the wrong choice given the behavior that's expected for floating-point types. The intent is to discuss the type stored in lieu of T, because SG1 believes that atomic<T> doesn't contain a T.
This is a note, so we don't have to be super-precise. I just used "object representation" instead of "underlying type", which is sufficiently vague about how the T's are actually stored.
The note in [atomics.types.operations] p23 says "if the underlying type has ..." but this is not the same meaning of "underlying type" used elsewhere ([basic.fundamental] and [dcl.enum]).
[atomics.types.generic] uses the phrase "the template argument for
T
", and the nested typevalue_type
is also defined. Either would be better than "the underlying type", but I think the note would be improved by referring to "object representation of the type", possibly even making use ofstd::has_unique_object_representations
.The text was updated successfully, but these errors were encountered: