P2025 Guaranteed copy elision for named return objects

[wg21bot]

P2025R0 Guaranteed copy elision for named return objects (Anton Zhilin)

[theres-waldo]

EWG-I in Prague

Poll: Forward P2025R0 to EWG as presented?

SF	F	N	A	SA
3	2	2	0	0

Consensus

Next steps for paper: Take it to EWG.

[jfbastien]

EWG Prague on Friday afternoon:

Mark this paper as tentatively ready to forward to Core.

SF	F	N	A	SA
3	8	5	3	0

[jfbastien]

Comments were received on this paper, we'll re-discuss in EWG.

[wg21bot]

P2025R1 Guaranteed copy elision for return variables (Anton Zhilin)

[erichkeane]

EWG discussed this in the 7/16 telecon, polls are as follows:

This paper should explore an explicit syntax to opt-into this functionality:

SF	F	N	A	SA
6	10	3	1	2

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:

SF	F	N	A	SA
3	5	6	4	0

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:

SF	F	N	A	SA
0	7	10	1	0

Conclusion: Weak consensus (note the high Neutral count) that we would like to see a paper on this topic in the future.

[wg21bot]

P2025R2 Guaranteed copy elision for return variables (Anton Zhilin)

[jfbastien]

D2025r3 was seen in today's EWG telecon.

We are interested in pursuing work on guaranteed copy elision for named return objects.

SF	F	N	A	SA
8	12	2	0	0

Send D2025r3 as-is to EWG electronic polling, with the intent of forwarding it to Core for C++23.

SF	F	N	A	SA
0	0	0	8	10