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
It is unclear in the current wording that the value representation of u includes all the bits that are part of the n member, not just the bits that are part of the c member, however that is the intent (and the upcoming compare_exchange_* wording depends on that). We should clarify that the set of bits in the value representation depends only on the type, and not on which value of that type we are considering.
The text was updated successfully, but these errors were encountered:
jensmaurer
changed the title
definition of "value representation" unnecessarily vague
[basic.types] p4: definition of "value representation" unnecessarily vague
Jun 8, 2018
[As discussed in CWG on 2018-06-07] Consider:
It is unclear in the current wording that the value representation of
u
includes all the bits that are part of then
member, not just the bits that are part of thec
member, however that is the intent (and the upcomingcompare_exchange_*
wording depends on that). We should clarify that the set of bits in the value representation depends only on the type, and not on which value of that type we are considering.The text was updated successfully, but these errors were encountered: