public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug libstdc++/78830] std::prev accepts ForwardIterator-s
[not found] <bug-78830-4@http.gcc.gnu.org/bugzilla/>
@ 2020-09-28 16:11 ` redi at gcc dot gnu.org
2020-09-28 16:46 ` redi at gcc dot gnu.org
` (2 subsequent siblings)
3 siblings, 0 replies; 4+ messages in thread
From: redi at gcc dot gnu.org @ 2020-09-28 16:11 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78830
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |lesley at lesleylai dot info
--- Comment #13 from Jonathan Wakely <redi at gcc dot gnu.org> ---
*** Bug 97232 has been marked as a duplicate of this bug. ***
^ permalink raw reply [flat|nested] 4+ messages in thread
* [Bug libstdc++/78830] std::prev accepts ForwardIterator-s
[not found] <bug-78830-4@http.gcc.gnu.org/bugzilla/>
2020-09-28 16:11 ` [Bug libstdc++/78830] std::prev accepts ForwardIterator-s redi at gcc dot gnu.org
@ 2020-09-28 16:46 ` redi at gcc dot gnu.org
2020-09-28 17:19 ` akrzemi1 at gmail dot com
2020-09-28 17:26 ` akrzemi1 at gmail dot com
3 siblings, 0 replies; 4+ messages in thread
From: redi at gcc dot gnu.org @ 2020-09-28 16:46 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78830
--- Comment #14 from Jonathan Wakely <redi at gcc dot gnu.org> ---
There is an LWG issue requesting clarification in the standard:
https://wg21.link/lwg3197
Option B is consistent with the interpretation of libstdc++ (and recent
versions of libc++). If Option A or C is accepted, I will change libstdc++
accordingly. Until then, I maintain that we conform to the standard as
currently written.
^ permalink raw reply [flat|nested] 4+ messages in thread
* [Bug libstdc++/78830] std::prev accepts ForwardIterator-s
[not found] <bug-78830-4@http.gcc.gnu.org/bugzilla/>
2020-09-28 16:11 ` [Bug libstdc++/78830] std::prev accepts ForwardIterator-s redi at gcc dot gnu.org
2020-09-28 16:46 ` redi at gcc dot gnu.org
@ 2020-09-28 17:19 ` akrzemi1 at gmail dot com
2020-09-28 17:26 ` akrzemi1 at gmail dot com
3 siblings, 0 replies; 4+ messages in thread
From: akrzemi1 at gmail dot com @ 2020-09-28 17:19 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78830
--- Comment #15 from Andrzej Krzemienski <akrzemi1 at gmail dot com> ---
How come?
[algorithms.requirements], paragraph 4, bullet 5
(http://eel.is/c++draft/algorithms#requirements-4.5) says:
If an algorithm's template parameter is named BidirectionalIterator,
BidirectionalIterator1, or BidirectionalIterator2, the template argument shall
meet the Cpp17BidirectionalIterator requirements
^ permalink raw reply [flat|nested] 4+ messages in thread
* [Bug libstdc++/78830] std::prev accepts ForwardIterator-s
[not found] <bug-78830-4@http.gcc.gnu.org/bugzilla/>
` (2 preceding siblings ...)
2020-09-28 17:19 ` akrzemi1 at gmail dot com
@ 2020-09-28 17:26 ` akrzemi1 at gmail dot com
3 siblings, 0 replies; 4+ messages in thread
From: akrzemi1 at gmail dot com @ 2020-09-28 17:26 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78830
--- Comment #16 from Andrzej Krzemienski <akrzemi1 at gmail dot com> ---
Oh, I see. The above requirement applies only to chapter Algorithms library.
Not Iterators library. Sorry.
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2020-09-28 17:26 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <bug-78830-4@http.gcc.gnu.org/bugzilla/>
2020-09-28 16:11 ` [Bug libstdc++/78830] std::prev accepts ForwardIterator-s redi at gcc dot gnu.org
2020-09-28 16:46 ` redi at gcc dot gnu.org
2020-09-28 17:19 ` akrzemi1 at gmail dot com
2020-09-28 17:26 ` akrzemi1 at gmail dot com
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).