This is an unofficial snapshot of the ISO/IEC JTC1 SC22 WG21 Core Issues List revision 119a. See http://www.open-std.org/jtc1/sc22/wg21/ for the official list.
2025-12-20
[Accepted as a DR at the November, 2024 meeting.]
P0135R1(Wording for guaranteed copy elision through simplified valuecategories) removes complete type requirements from7.6.1.3 [expr.call] (under the assumption that subclause9.5 [dcl.init] has them; apparently it does not) and from7.6.1.8 [expr.typeid] paragraph 3. These both appear to be badchanges and should presumably be reverted.
Additional notes (October, 2024)
An almost-editorial change (approved by CWG 2021-08-24) restored aconsistent complete-type requirement fortypeid; seecplusplus/draft#4827.
Proposed resolution (approved by CWG 2024-10-25):
Change in 7.6.1.3 [expr.call] paragraph 13 as follows:
A function call is an lvalue if the result type is an lvalue referencetype or an rvalue reference to function type, an xvalue if the resulttype is an rvalue reference to object type, and a prvalue otherwise.If it is a non-void prvalue, the type of the functioncall expression shall be complete, except as specified in9.2.9.6 [dcl.type.decltype].