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
Issue description: [basic.types.general] first defines the value representation as
the set of bits in the object representation [...] that participate in representing a value
Later, in the same paragraph, it says
For trivially copyable types, the value representation is a set of bits in the object representation that determines a value, [...]
It is unclear what difference, if any, is meant between "participate in representing a value" and "determines a value". If they mean the same thing, then it is not clear why one of these statements applies only to trivially copyable types.
There does not appear to be any behavior in the standard that depends upon the value representation of a type that is not trivially copyable.
[...] The value representation of a trivially copyable type T is the set of bits in the object representation of T that participate in representing a valuevalue of type T, which is one discrete element of an implementation-defined set of values. [...] For trivially copyable types, the value representation is a set of bits in the object representation that determines a value, which is one discrete element of an implementation-defined set of values.
The text was updated successfully, but these errors were encountered:
jensmaurer
changed the title
[basic.types.general] Does value representation exist for non-trivially-copyable types?
CWG2953 [basic.types.general] Does value representation exist for non-trivially-copyable types?
Nov 8, 2024
Full name of submitter: Brian Bi
Issue description: [basic.types.general] first defines the value representation as
Later, in the same paragraph, it says
It is unclear what difference, if any, is meant between "participate in representing a value" and "determines a value". If they mean the same thing, then it is not clear why one of these statements applies only to trivially copyable types.
There does not appear to be any behavior in the standard that depends upon the value representation of a type that is not trivially copyable.
Suggested resolution: Edit [basic.types.general]/4:
The text was updated successfully, but these errors were encountered: