Title
Description of binding to rvalue-references should use the new 'xvalue' vocabulary
Status
c++11
Section
[res.on.arguments]
Submitter
INCITS

Created on 2010-08-25.00:00:00 last changed 86 months ago

Messages

Date: 2017-03-21.22:56:50

Proposed resolution:

Amend the note in 17.6.3.9 [res.on.arguments] p1 bullet 3.

[ Note: If a program casts an lvalue to an rvaluexvalue while passing that lvalue to a library function (e.g. by calling the function with the argument move(x)), the program is effectively asking that function to treat that lvalue as a temporary. The implementation is free to optimize away aliasing checks which might be needed if the argument was anlvalue. — end note]

Date: 2017-03-21.22:56:50

[ Adopted at 2010-11 Batavia ]

Date: 2017-03-21.22:56:50

[ Batavia: Immediate ]

Date: 2017-03-21.22:56:50

[ Pre-Batavia: ]

Walter Brown provides wording.

Date: 2017-03-21.22:56:50

[ Resolution proposed by the ballot comment: ]

Rephrase the Note in terms of xvalue.

Date: 2010-10-31.13:59:49

Addresses US-82

[res.on.arguments] p.1. b.3: The second Note can benefit by adopting recent nomenclature.

History
Date User Action Args
2017-03-21 22:56:50adminsetmessages: + msg9141
2017-03-21 22:56:50adminsetmessages: + msg9140
2017-03-21 22:56:50adminsetmessages: + msg9139
2017-03-21 22:56:50adminsetmessages: + msg9138
2011-08-23 20:07:26adminsetstatus: wp -> c++11
2010-11-14 13:10:57adminsetstatus: voting -> wp
2010-11-13 01:17:02adminsetstatus: open -> voting
2010-11-13 01:11:40adminsetstatus: immediate -> open
2010-11-08 22:47:24adminsetstatus: open -> immediate
2010-11-08 03:13:15adminsetmessages: + msg5310
2010-10-24 10:50:39adminsetmessages: + msg4992
2010-08-25 00:00:00admincreate