diff options
author | Patrick Palka <ppalka@redhat.com> | 2020-03-02 19:39:46 -0500 |
---|---|---|
committer | Patrick Palka <ppalka@redhat.com> | 2020-03-03 22:44:39 -0500 |
commit | 144dfc68d0c0f5b99a0cd0a14b211f82afed88c6 (patch) | |
tree | fce1c69a345fe914fd8b7962e6277a183d155ebb /gcc | |
parent | 26af9cd8af1b3b603434586a17127d8c3d2d8266 (diff) | |
download | gcc-144dfc68d0c0f5b99a0cd0a14b211f82afed88c6.zip gcc-144dfc68d0c0f5b99a0cd0a14b211f82afed88c6.tar.gz gcc-144dfc68d0c0f5b99a0cd0a14b211f82afed88c6.tar.bz2 |
libstdc++: Move-only input iterator support in <memory> algorithms (LWG 3355)
This adds support for move-only input iterators in the ranges::unitialized_*
algorithms defined in <memory>, as per LWG 3355. The only changes needed are to
add calls to std::move in the appropriate places and to use operator- instead of
ranges::distance because the latter cannot be used with a move-only iterator
that has a sized sentinel, as is the case here. (This issue with
ranges::distance is LWG 3392.)
libstdc++-v3/ChangeLog:
LWG 3355 The memory algorithms should support move-only input iterators
introduced by P1207
* include/bits/ranges_uninitialized.h
(__uninitialized_copy_fn::operator()): Use std::move to avoid attempting
to copy __ifirst, which could be a move-only input iterator. Use
operator- instead of ranges::distance to compute distance from a sized
sentinel.
(__uninitialized_copy_n_fn::operator()): Likewise.
(__uninitialized_move_fn::operator()): Likewise.
(__uninitialized_move_n_fn::operator()): Likewise.
(__uninitialized_destroy_fn::operator()): Use std::move to avoid
attempting to copy __first.
(__uninitialized_destroy_n_fn::operator()): Likewise.
* testsuite/20_util/specialized_algorithms/destroy/constrained.cc:
Augment test.
* .../specialized_algorithms/uninitialized_copy/constrained.cc:
Likewise.
* .../specialized_algorithms/uninitialized_move/constrained.cc:
Likewise.
Diffstat (limited to 'gcc')
0 files changed, 0 insertions, 0 deletions