This is an unofficial snapshot of the ISO/IEC JTC1 SC22 WG21 Core Issues List revision 116a. See http://www.open-std.org/jtc1/sc22/wg21/ for the official list.

2024-12-19

877. Viable functions and binding references to rvalues

[Voted into WP at October, 2009 meeting.]

12.2.3 [over.match.viable] paragraph 3 says,

If the parameter has reference type, the implicit conversion sequence includes the operation of binding the reference, and the fact that a reference to non-const cannot be bound to an rvalue can affect the viability of the function (see 12.2.4.2.5 [over.ics.ref]).

This should say “lvalue reference to non-const,” as is correctly stated in 12.2.4.2.5 [over.ics.ref] paragraph 3.

Proposed resolution (July, 2009):

Change 12.2.3 [over.match.viable] paragraph 3 as follows:

If the parameter has reference type, the implicit conversion sequence includes the operation of binding the reference, and the fact that a an lvalue reference to non-const cannot be bound to an rvalue can affect the viability of the function (see 12.2.4.2.5 [over.ics.ref]).