This is the mail archive of the libstdc++@gcc.gnu.org mailing list for the libstdc++ 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]

[v3 PATCH] Implement LWG 2353

From: Ville Voutilainen <ville dot voutilainen at gmail dot com>
To: "libstdc++" <libstdc++ at gcc dot gnu dot org>, "gcc-patches at gcc dot gnu dot org" <gcc-patches at gcc dot gnu dot org>
Date: Sun, 19 Nov 2017 02:40:21 +0200
Subject: [v3 PATCH] Implement LWG 2353
Authentication-results: sourceware.org; auth=none

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

Follow-Ups:
- Re: [v3 PATCH] Implement LWG 2353
  - From: Ville Voutilainen
- Re: [v3 PATCH] Implement LWG 2353
  - From: Jonathan Wakely

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]