This page is a snapshot from the LWG issues list, see the Library Active Issues List for more information and the meaning of WP status.
Section: 20.4.2 [pairs.pair], 220.127.116.11 [tuple.assign] Status: WP Submitter: Casey Carter Opened: 2017-05-05 Last modified: 2020-09-06
View other active issues in [pairs.pair].
View all other issues in [pairs.pair].
View all issues with WP status.
LWG 2729 constrained many pair & tuple assignment operators to "not participate in overload resolution" and "be defined as deleted if." As discussed when LWG reviewed 2756, it is undesirable to require that a move constructor or assignment operator be "defined as deleted," since it is unclear whether that operation should be implicitly deleted, and therefore not participate in overload resolution, or explicitly deleted and therefore impede overload resolution for usages that would otherwise find copies.
[2017-07 Toronto Wed Issue Prioritization]
[2017-11 Albuquerque Wednesday issue processing]
Move to Immediate
This wording is relative to N4659.
Edit 20.4.2 [pairs.pair] as indicated:
pair& operator=(pair&& p) noexcept(see below);
-21- Effects: Assigns to first with std::forward<first_type>(p.first) and to second with std::forward<second_type>(p.second).-22- Remarks: This operator shall
be defined as deletedunless is_move_assignable_v<first_type> is true and is_move_assignable_v<second_type> is true. […]
Edit 18.104.22.168 [tuple.assign] as indicated:
tuple& operator=(tuple&& u) noexcept(see below);
-5- Effects: For all i, assigns std::forward<Ti>(get<i>(u)) to get<i>(*this).-6- Remarks: This operator shall
be defined as deletedunless is_move_assignable_v<Ti> is true for all i. […]