Proposed resolution:

This wording is relative to N5054.

1. Modify [iterator.concept.winc] as indicated:

   -9- All integer-class types are structural types ([temp.param]) that model `regular` ([concepts.object]) and three_way_comparable<strong_ordering> ([cmp.concept]). Two values of an integer-class type are template-argument-equivalent if and only if they are equal.

[ 2026-07-31 LWG telecon; Status changed: New → Ready. ]

[ 2026-07-30; Tim provides new wording ]

[ 2026-05-29; Reflector poll. ]

Set priority to 3 after reflector poll.

Need additional statement clarifying when the types are template-argument-equivalent.

Currently, integer-class types are not guaranteed to be structural types, so the range of size members that return integer-class types may not be able to model tiny-range, because its size value cannot be used as a template argument even if it is a constant expression. This does not appear to be the intention.

Given that integer-class types should behave like regular integers, and those types in MSVC-STL and libstdc++ are both implemented as structural types, it would be better to be clear about the wording.