From: Jonathan Wakely <jwakely@redhat.com>
To: "François Dumont" <frs.dumont@gmail.com>
Cc: "libstdc++" <libstdc++@gcc.gnu.org>,
gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH][_GLIBCXX_DEBUG] Fix std::__niter_base behavior
Date: Wed, 14 Feb 2024 19:44:20 +0000 [thread overview]
Message-ID: <CACb0b4nbX5fPL=G7S8hDSne37Rga5MsGaUC7VN759ypuKJYGUQ@mail.gmail.com> (raw)
In-Reply-To: <4c78d538-da4d-4a54-987d-3c4257913035@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1295 bytes --]
On Wed, 14 Feb 2024 at 18:39, François Dumont <frs.dumont@gmail.com> wrote:
> libstdc++: [_GLIBCXX_DEBUG] Fix std::__niter_base behavior
>
> std::__niter_base is used in _GLIBCXX_DEBUG mode to remove _Safe_iterator<>
> wrapper on random access iterators. But doing so it should also preserve
> original
> behavior to remove __normal_iterator wrapper.
>
> libstdc++-v3/ChangeLog:
>
> * include/bits/stl_algobase.h (std::__niter_base): Redefine the
> overload
> definitions for __gnu_debug::_Safe_iterator.
> * include/debug/safe_iterator.tcc (std::__niter_base): Adapt
> declarations.
>
> Ok to commit once all tests completed (still need to check pre-c++11) ?
>
The declaration in include/bits/stl_algobase.h has a noexcept-specifier
but the definition in include/debug/safe_iterator.tcc does not have one -
that seems wrong (I'm surprised it even compiles).
Just using std::is_nothrow_copy_constructible<_Ite> seems simpler, that
will be true for __normal_iterator<I, C> if
is_nothrow_copy_constructible<I> is true.
The definition in include/debug/safe_iterator.tcc should use
std::declval<_Ite>() not declval<_Ite>(). Is there any reason why the
definition uses a late-specified-return-type (i.e. auto and ->) when the
declaration doesn't?
next prev parent reply other threads:[~2024-02-14 19:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-14 18:39 François Dumont
2024-02-14 19:44 ` Jonathan Wakely [this message]
2024-02-14 21:48 ` François Dumont
2024-02-15 13:17 ` Jonathan Wakely
2024-02-15 18:38 ` François Dumont
2024-02-15 18:40 ` Jonathan Wakely
2024-02-17 14:14 ` François Dumont
2024-02-19 7:07 ` Stephan Bergmann
2024-02-19 8:12 ` Jonathan Wakely
2024-02-19 8:21 ` Jonathan Wakely
2024-02-19 18:39 ` François Dumont
2024-02-20 18:42 ` François Dumont
2024-02-20 19:27 ` Jonathan Wakely
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CACb0b4nbX5fPL=G7S8hDSne37Rga5MsGaUC7VN759ypuKJYGUQ@mail.gmail.com' \
--to=jwakely@redhat.com \
--cc=frs.dumont@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=libstdc++@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).