This is an unofficial snapshot of the ISO/IEC JTC1 SC22 WG21 Core Issues List revision 121a. See http://www.open-std.org/jtc1/sc22/wg21/ for the official list.
2026-11-19
C++26 DIS comment **-066
Subclause 7.6.19 [expr.assign] paragraph 7 uses "shall" twice in connection with undefined behavior, which is not in harmony with the rest of the core language phraseology.
Possible resolution [SUPERSEDED]:
Change in 7.6.19 [expr.assign] paragraph 7 as follows:
If the value being stored in an object is read via another object that overlaps in any way the storage of the first object,thenthe behavior is undefined unless the overlapshall beis exact and the two objectsshallhave the same type, otherwise the behavior is undefined.
Proposed resolution (approved by CWG 2026-11-19):
Change in 7.6.19 [expr.assign] paragraph 7 as follows:
If the value being stored in an object is read via another object that overlaps in any way the storage of the first object, thenand
- the overlap
shall beis not exactandor- the two objects
shalldo not have the same type,otherwisethe behavior is undefined.