New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
P2830 R3 Standardized Constexpr Type Ordering #1507
Comments
EWGI discussed P2830R1 during the Tuesday Afternoon session in Kona. The following poll was taken. EWGI believes the use cases from P2830R1 are sufficiently motivated, and would like to see a future revision that covers the issues discussed in the room.
Result: Consensus |
P2830R1 constexpr type comparison (Gašper Ažman, Nathan Nichols) |
EWGI discussed P2380R2 during the Thursday afternoon session in Tokyo. The following poll was taken: EWGI believes P2830R2 is sufficiently well developed, EWGI forwards it to EWG (as well as being seen by SG7 and SG18).
Result: Consensus |
P2830R2 Standardized Constexpr Type Ordering (Gašper Ažman, Nathan Nichols) |
P2830R3 Standardized Constexpr Type Ordering (Gašper Ažman, Nathan Nichols) |
P2830R3 was discussed during the April 17th EWG Telecon. The following polls were taken: P2830R3: EWG prefers the library entry point for total ordering of types rather than a language level solution.
Result: Consensus P2830R3: EWG approves of the 'implementation defined' behavior of type_order_v, as opposed to a best-effort well-defined standard ordering on a best-effort subset of types(Consensus called both ways).
Result: Not Consensus Either Way |
@erichkeane When you are happy with the design, please tag LEWG so that we can do a ML review to discuss the names of the library interface. Thanks! |
P2830R0 constexpr type comparison (Gašper Ažman, Nathan Nichols)
The text was updated successfully, but these errors were encountered: