- Title
- Viable functions and binding references to rvalues
- Status
- cd2
- Section
- 12.2.3 [over.match.viable]
- Submitter
- Daniel Krügler
Created on 2009-04-23.00:00:00 last changed 190 months ago
Messages
Date: 2009-10-15.00:00:00
[Voted into WP at October, 2009 meeting.]
Date: 2009-07-15.00:00:00
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 thataan 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]).
Date: 2009-04-23.00:00:00
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.
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2010-03-29 00:00:00 | admin | set | status: dr -> cd2 |
| 2009-11-08 00:00:00 | admin | set | messages: + msg2471 |
| 2009-11-08 00:00:00 | admin | set | status: ready -> dr |
| 2009-08-03 00:00:00 | admin | set | messages: + msg2174 |
| 2009-08-03 00:00:00 | admin | set | status: open -> ready |
| 2009-04-23 00:00:00 | admin | create | |