Issue 3575: <=> for integer-class types isn't consistently specified

Title: <=> for integer-class types isn't consistently specified
Status: resolved
Section: [iterator.concept.winc]
Submitter: Jiang An

Created on 2021-07-25.00:00:00 last changed 37 months ago

Messages

Date: 2021-10-23.00:00:00

[ 2021-10-23 Resolved by the adoption of P2393R1 at the October 2021 plenary. Status changed: Tentatively Resolved → Resolved. ]

msg11988 (view)

Date: 2021-08-15.00:00:00

[ 2021-08-20; Reflector poll ]

Set priority to 3 after reflector poll. Tentatively Resolved by P2393R1 which has been approved by LWG.

msg11979 (view)

Date: 2021-07-15.00:00:00

[ 2021-07-31, Daniel comments ]

The upcoming revision P2393R1 will provide additional wording to solve this issue.

msg11976 (view)

Date: 2021-07-25.00:00:00

It seems that the return type of <=> for integer-class types is not specified consistently with other comparison operators. Even P2393R0 has ignored it.

IMO strong_ordering should be added to [iterator.concept.winc]/(5.3), and three_way_comparable<strong_ordering> should be added to [iterator.concept.winc]/8.

History
Date	User	Action	Args
2021-10-23 11:04:22	admin	set	messages: + msg12180
2021-08-20 17:03:35	admin	set	messages: + msg11988
2021-08-20 17:03:35	admin	set	status: new -> resolved
2021-07-31 10:53:29	admin	set	messages: + msg11979
2021-07-25 00:00:00	admin	create