Jonathan Wakely 7825399092 libstdc++: Use correct argument type for __use_alloc, again [PR 96803] ... While backporting 5494edae83 I noticed that it's still not correct. I made the allocator-extended constructor use the right type for the uses-allocator construction detection, but I used an rvalue when it should be a const lvalue. This should fix it properly this time. libstdc++-v3/ChangeLog: PR libstdc++/96803 * include/std/tuple (_Tuple_impl(allocator_arg_t, Alloc, const _Tuple_impl<U...>&)): Use correct value category in __use_alloc call. * testsuite/20_util/tuple/cons/96803.cc: Check with constructors that require correct value category to be used.		2020-09-22 08:42:18 +01:00
..
apply
comparison_operators	libstdc++: Remove inheritance from elements in std::tuple	2020-08-17 15:27:51 +01:00
cons	libstdc++: Use correct argument type for __use_alloc, again [PR 96803]	2020-09-22 08:42:18 +01:00
creation_functions	libstdc++: Remove inheritance from elements in std::tuple	2020-08-17 15:27:51 +01:00
element_access	libstdc++: Remove inheritance from elements in std::tuple	2020-08-17 15:27:51 +01:00
make_from_tuple
requirements
48476.cc
51365.cc
53648.cc
56785.cc
60497.cc
61947.cc
67844.cc
77395.cc
77802.cc
78939.cc
constexpr_swap.cc
cv_tuple_element.cc
cv_tuple_size_neg.cc
cv_tuple_size.cc
dr2729.cc
moveable2.cc
moveable.cc
noexcept_move_assign.cc
noexcept_swap.cc
swap_cxx17.cc
swap.cc
tuple_element_t.cc
tuple_element.cc
tuple_size_v.cc
tuple_size.cc