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 seems that "the same" and "identical" have different meaning in [temp.type]/2, but the meaning of "identical" is unclear.
The intended meaning of "identical values" might be "identical value representations" (P1714R1), but "value representations" is not used when cooperated into P1907R1.
Should we use "value representations" here?
The text was updated successfully, but these errors were encountered:
It's deliberate that we do not use "value representations". There are environments in which the same number can be exactly represented as both a normalized and a non-normalized floating point value, with distinct value representations, and we did not intend to require that they be treated as different.
I agree that the exact rules are unclear, but I think that's not something that can be fixed editorially. (It's also hard to fix this non-editorially since the C++ core language currently has no notion of NaN values, normalization, and other similar things you would need to take into account to specify rules here.)
It seems that "the same" and "identical" have different meaning in [temp.type]/2, but the meaning of "identical" is unclear.
The intended meaning of "identical values" might be "identical value representations" (P1714R1), but "value representations" is not used when cooperated into P1907R1.
Should we use "value representations" here?
The text was updated successfully, but these errors were encountered: