P2025 Guaranteed copy elision for named return objects #756
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.
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.