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?
to your account
P2025R0 Guaranteed copy elision for named return objects (Anton Zhilin)
The text was updated successfully, but these errors were encountered:
EWG-I in Prague
Poll: Forward P2025R0 to EWG as presented?
Next steps for paper: Take it to EWG.
Sorry, something went wrong.
EWG Prague on Friday afternoon:
Mark this paper as tentatively ready to forward to Core.
Comments were received on this paper, we'll re-discuss in EWG.
P2025R1 Guaranteed copy elision for return variables (Anton Zhilin)
EWG discussed this in the 7/16 telecon, polls are as follows:
This paper should explore an explicit syntax to opt-into this functionality:
Conclusion: This paper needs to explore an explicit opt-in syntax and return to EWG.
This paper should explore a syntax that annotates a return/call for the purposes of diagnostics:
Conclusion: EWG was not convinced that an annotation for a return/call to guide diagnostics was necessary to return to EWG.
Another paper should explore a syntax that annotates a return/call for the purposes of diagnostics:
Conclusion: Weak consensus (note the high Neutral count) that we would like to see a paper on this topic in the future.
P2025R2 Guaranteed copy elision for return variables (Anton Zhilin)
D2025r3 was seen in today's EWG telecon.
We are interested in pursuing work on guaranteed copy elision for named return objects.
Send D2025r3 as-is to EWG electronic polling, with the intent of forwarding it to Core for C++23.
No branches or pull requests