P2025 Guaranteed copy elision for named return objects #756
Comments
Poll: Forward P2025R0 to EWG as presented?
Consensus Next steps for paper: Take it to EWG. |
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. |
P2025R0 Guaranteed copy elision for named return objects (Anton Zhilin)
The text was updated successfully, but these errors were encountered: