-
Notifications
You must be signed in to change notification settings - Fork 18
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
P1938 if consteval #677
Comments
See the polls from the Belfast discussion of FR222: |
EWG Prague on Friday morning: Reviewing R1 of the paper, which wasn’t in the mailing. Can’t poll for tentative ready in this meeting. We are interested in some solution in the space which this paper tackles, either as proposed in the paper or in some other form.
Consensus. We want to pursue this paper for C++23.
Given how many neutrals we have here, and none in the first poll, this isn't consensus. People interested in other options should come with new information by next meeting to help increase consensus. |
P1938R1 if consteval (Barry Revzin, Daveed Vandevoorde, Richard Smith, Andrew Sutton) |
Discussed in today's EWG telecon. Polls: if consteval should be parenthesized as if (consteval) ...
if consteval should not require braces, making this valid: if consteval boom(); else bam();
if consteval is tentatively ready to be voted on to forward to Core, after updating the paper as discussed
|
P1938R2 if consteval (Barry Revzin, Daveed Vandevoorde, Richard Smith, Andrew Sutton) |
Poll: Forward P1938R2 "if consteval" to Core.
Poll outcome: ✅ consensus. Salient comments:
|
CWG 2021-03-22: Approved D1938R3. |
LWG review planned for 2021-04-02 |
Change of plan, 2021-04-09 instead. |
Now schedule 2021-04-16 |
LWG reviewed and adopted library wording. https://wiki.edg.com/bin/view/Wg21telecons2021/P1938-20210416 Adopt P1938R3 if consteval for c++23 |
P1938R3 if consteval (Barry Revzin, Daveed Vandevoorde, Richard Smith, Andrew Sutton) |
Adopted 2021-06. |
P1938R0 if consteval (Barry Revzin, Daveed Vandevoorde, Richard Smith)
The text was updated successfully, but these errors were encountered: