Louis Dionne a0839b14df [libc++] Fix tuple assignment from types derived from a tuple-like
The implementation of tuple's constructors and assignment operators
currently diverges from the way the Standard specifies them, which leads
to subtle cases where the behavior is not as specified. In particular, a
class derived from a tuple-like type (e.g. pair) can't be assigned to a
tuple with corresponding members, when it should. This commit re-implements
the assignment operators (BUT NOT THE CONSTRUCTORS) in a way much closer
to the specification to get rid of this bug. Most of the tests have been
stolen from Eric's patch https://reviews.llvm.org/D27606.

As a fly-by improvement, tests for noexcept correctness have been added
to all overloads of operator=. We should tackle the same issue for the
tuple constructors in a future patch - I'm just trying to make progress
on fixing this long-standing bug.

PR17550
rdar://15837420

Differential Revision: https://reviews.llvm.org/D50106
2021-02-22 14:52:18 -05:00

73 lines
2.5 KiB
C++

//===----------------------------------------------------------------------===//
//
// Part of the LLVM Project, under the Apache License v2.0 with LLVM Exceptions.
// See https://llvm.org/LICENSE.txt for license information.
// SPDX-License-Identifier: Apache-2.0 WITH LLVM-exception
//
//===----------------------------------------------------------------------===//
// <tuple>
// template <class... Types> class tuple;
// template <class U1, class U2>
// tuple& operator=(const pair<U1, U2>& u);
// UNSUPPORTED: c++03
#include <cassert>
#include <memory>
#include <tuple>
#include <type_traits>
#include <utility>
struct NothrowCopyAssignable {
NothrowCopyAssignable& operator=(NothrowCopyAssignable const&) noexcept { return *this; }
};
struct PotentiallyThrowingCopyAssignable {
PotentiallyThrowingCopyAssignable& operator=(PotentiallyThrowingCopyAssignable const&) { return *this; }
};
#include "test_macros.h"
int main(int, char**)
{
{
typedef std::pair<long, char> T0;
typedef std::tuple<long long, short> T1;
T0 t0(2, 'a');
T1 t1;
t1 = t0;
assert(std::get<0>(t1) == 2);
assert(std::get<1>(t1) == short('a'));
}
{
// test that the implicitly generated copy assignment operator
// is properly deleted
using T = std::tuple<int, int>;
using P = std::tuple<std::unique_ptr<int>, std::unique_ptr<int>>;
static_assert(!std::is_assignable<T, const P &>::value, "");
}
{
typedef std::tuple<NothrowCopyAssignable, long> Tuple;
typedef std::pair<NothrowCopyAssignable, int> Pair;
static_assert(std::is_nothrow_assignable<Tuple&, Pair const&>::value, "");
static_assert(std::is_nothrow_assignable<Tuple&, Pair&>::value, "");
static_assert(std::is_nothrow_assignable<Tuple&, Pair const&&>::value, "");
}
{
typedef std::tuple<PotentiallyThrowingCopyAssignable, long> Tuple;
typedef std::pair<PotentiallyThrowingCopyAssignable, int> Pair;
static_assert(std::is_assignable<Tuple&, Pair const&>::value, "");
static_assert(!std::is_nothrow_assignable<Tuple&, Pair const&>::value, "");
static_assert(std::is_assignable<Tuple&, Pair&>::value, "");
static_assert(!std::is_nothrow_assignable<Tuple&, Pair&>::value, "");
static_assert(std::is_assignable<Tuple&, Pair const&&>::value, "");
static_assert(!std::is_nothrow_assignable<Tuple&, Pair const&&>::value, "");
}
return 0;
}