Section: 24.3.4.4 [iterator.concept.winc] Status: Resolved Submitter: Casey Carter Opened: 2020-01-07 Last modified: 2021-10-23
Priority: 3
View all other issues in [iterator.concept.winc].
View all issues with Resolved status.
Discussion:
The working draft ignores the possibility that:
the value of an expression of integer-class type might not be representable by the target integer type of a conversion, and
the value of an expression of integer type might not be representable by the target integer-class type of a conversion.
Presumably the behavior of these cases is undefined by omission; is this actually the intent?
Notably (2) could be specified away by mandating that all integer-class types are capable of representing the value range of all integer types of the same signedness.[2020-01-25 Issue Prioritization]
Priority to 3 after reflector discussion.
[2021-10-23 Resolved by the adoption of P2393R1 at the October 2021 plenary. Status changed: New → Resolved.]
Proposed resolution: