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
P2350 constexpr class #1028
Comments
We saw this paper in yesterday's EWG telecon: POLL: we are interested in pursuing a way to specify that multiple/all class members are constexpr, either as suggested in this paper or through another mechanism, considering that time is limited and there is only so much work we can do.
Result: consensus. POLL: support class-level consteval at the same time or before supporting constexpr, to inform the design of class constexpr.
Result: consensus. POLL: use access specifier constexpr instead of class-level constexpr.
Result: no consensus. POLL: class-level constexpr should also affect friend functions.
Result: no consensus. POLL: it should be ill-formed to put constexpr on a class which can’t be entirely constexpr (e.g. because of its base or data members not being constexpr).
Result: no consensus. POLL: static data members should also be constexpr in a constexpr class.
Result: consensus. POLL: allow constexpr and final to appear in either order.
Result: consensus. |
P2350R1 constexpr class (Andreas Fertig) |
Seen in today's EWG telecon: POLL: having seen what class-level consteval looks like, we still want it in P2350.
Result: consensus against, we don’t want consteval in P2350. POLL: send P2350 to electronic polling, targeting CWG for C++23.
Result: consensus. POLL: given that Committee time is limited, we’d like to see a different paper which further explores class-level consteval.
Result: consensus. POLL: given that Committee time is limited, we’d like to see a different paper which proposes implicit constexpr.
Result: consensus. |
P2350R2 constexpr class (Andreas Fertig) |
Poll outcome: |
P2350R0 constexpr class (Andreas Fertig)
The text was updated successfully, but these errors were encountered: