This page is a snapshot from the LWG issues list, see the Library Active Issues List for more information and the meaning of C++11 status.
Section: 20.5.7 [tuple.elem] Status: C++11 Submitter: Alisdair Meredith Opened: 2009-08-18 Last modified: 2016-02-10
Priority: Not Prioritized
View all other issues in [tuple.elem].
View all issues with C++11 status.
The tuple get API should respect rvalues. This would allow for moving a single element out of a tuple-like type.
[ 2009-10-30 Alisdair adds: ]
The issue of rvalue overloads of get for tuple-like types was briefly discussed in Santa Cruz.
The feedback was this would be welcome, but we need full wording for the other types (pair and array) before advancing.
I suggest the issue moves to Open from New as it has been considered, feedback given, and it has not (yet) been rejected as NAD.
[ 2010 Rapperswil: ]
Note that wording has been provided, and this issue becomes more important now that we have added a function to support forwarding argument lists as tuples. Move to Tentatively Ready.
[ Adopted at 2010-11 Batavia ]
Add the following signature to p2 20.5.1 [tuple.general]
And again to 20.5.7 [tuple.elem].
Add the following signature to p1 20.2 [utility]
And to p5 20.4.4 [pair.astuple]
Add the following signature to 22.3 [sequences] <array> synopsis
And after p8 18.104.22.168 [array.tuple]