[2025-11 CWG Motion 2b] P3921R0 Core Language Working Group 'ready' Issues for the November, 2025 meeting: issue 1670#8490
Conversation
7955549 to
c40f633
Compare
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
|
You know what, I'm just going to submit an LWG issue for this. |
|
We have now LWG 4468 for this. |
|
Thanks, @Dani-Hub! |
|
It seems to me that the entire paragraph "A conversion function template shall not have a deduced return type" should go away. Technically, that might (?) actually be a normative change in that the current rule makes the template |
I wouldn't be opposed, but that seems more like CWG issue material than a drive-by fix in this PR which applies the motions. |
This comment was marked as resolved.
This comment was marked as resolved.
|
Is "Fixes FI-4 (C++14 CD)." correct? |
|
CWG1670 links to "N3690 comment FI 4". I'm not 100% sure about the hyphenation rules here; perhaps it should be "FI 4". |
|
Right, yes, I was thinking the same. Indeed, it fixes a long-standing issue, though I guess not relevant to the C++14 CD record of response... |
Also a late resolution of NB FI 4 (C++14 CD).
c40f633 to
1a315f5
Compare
Fixes #8456.
Partially fixes cplusplus/papers#2580
Fixes FI-4 (C++14 CD).
Also fixes cplusplus/papers#2409
Note that this PR also fixes an example in [class.conv.fct] that becomes clearly incorrect after CWG1670 is applied.