918. Swap for tuple needs to be conceptualized

Section: 23.5.3.3 [tuple.swap] Status: NAD Concepts Submitter: Daniel Krügler Opened: 2008-10-04 Last modified: 2016-02-10

Priority: Not Prioritized

View all issues with NAD Concepts status.

Discussion:

Issue 522 was accepted after tuple had been conceptualized, therefore this step needs to be completed.

[ Post Summit Daniel adds ]

This is now NAD Editorial (addressed by N2844) except for item 3 in the proposed wording.

[ 2009-05-01 Daniel adds: ]

As of the recent WP (N2857), this issue is now completely covered by editorial changes (including the third bullet), therefore I unconditionally recommend NAD.

[ Batavia (2009-05): ]

We observed that all the proposed changes have already been applied to the Working Draft, rendering this issue moot.

Move to NAD.

Proposed resolution:

  1. In both 23.5.1 [tuple.general]/2 and 23.5.3.10 [tuple.special] change

    template <class Swappable... Types>
    void swap(tuple<Types...>& x, tuple<Types...>& y);
    
  2. In 23.5.3 [tuple.tuple], class tuple definition and in 23.5.3.3 [tuple.swap], change

    requires Swappable<Types>...void swap(tuple&);
    
  3. In 23.5.3.3 [tuple.swap] remove the current requires-clause, which says:

    Requires: Each type in Types shall be Swappable