This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
The issue submission talks about ranges that have InputIterators as their iterator type. Even without any such range types, the added test more or less shows that it's draconian to require a ForwardIterator in std::next, since it seems perfectly reasonable to be able to std::next() an iterator of an istream. Testing on Linux-PPC64, ok for trunk if the full suite passes? 2017-11-19 Ville Voutilainen <ville.voutilainen@gmail.com> Implement LWG 2353 * include/bits/stl_iterator_base_funcs.h (next): Use InputIterator instead of ForwardIterator. * testsuite/24_iterators/operations/lwg2353.cc: New. * testsuite/24_iterators/operations/next_neg.cc: Remove.
Attachment:
lwg2353.diff
Description: Text document
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |