From: Jonathan Wakely <jwakely@redhat.com>
To: "François Dumont" <frs.dumont@gmail.com>
Cc: "libstdc++@gcc.gnu.org" <libstdc++@gcc.gnu.org>,
gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH][_GLIBCXX_DEBUG] Remove useless checks
Date: Mon, 23 Jan 2023 09:22:43 +0000 [thread overview]
Message-ID: <CACb0b4=2yVEUK_2i0nDgdbhQktvzvcRHqma0TeMQ5Nhva7=Zag@mail.gmail.com> (raw)
In-Reply-To: <dd643693-5e73-cd9f-ae2e-541d253985d0@gmail.com>
On Mon, 23 Jan 2023 at 06:02, François Dumont via Libstdc++
<libstdc++@gcc.gnu.org> wrote:
>
> libstdc++: [_GLIBCXX_DEBUG] Remove useless constructor checks
>
> Creating a safe iterator from a normal iterator is done within the
> library where we
> already know that it is done correctly. The rare situation where a
> user would use safe
> iterators for his own purpose is non-Standard code so outside
> _GLIBCXX_DEBUG scope. For
> those reasons the __msg_init_singular is useless and can be removed.
>
> Additionally in the copy constructor used for post-increment and
> post-decrement operators
> the __msg_init_copy_singular check can also be ommitted because of
> the preliminary
> __msg_bad_inc and __msg_bad_dec checks.
>
> libstdc++-v3/ChangeLog:
>
> * include/debug/safe_iterator.h
> (_Safe_iterator<>::_Unsafe_call): New.
I don't like the name "unsafe call". Why is it unsafe? As you say
above, we don't need to check because we know that it's only called in
a context where it's safe. Can we call it _Unchecked instead of
_Unsafe_call? That seems like a more accurate description of the
behaviour.
> (_Safe_iterator(const _Safe_iterator&, _Unsafe_call): New.
> (_Safe_iterator::operator++(int)): Use latter.
> (_Safe_iterator::operator--(int)): Likewise.
> (_Safe_iterator(_Iterator, const _Safe_sequence_base*)):
> Remove !_M_insular()
> check.
> * include/debug/safe_local_iterator.h
> (_Safe_local_iterator<>::_Unsafe_call):
> New.
> (_Safe_local_iterator(const _Safe_local_iterator&,
> _Unsafe_call): New.
> (_Safe_local_iterator::operator++(int)): Use latter.
> * src/c++11/debug.cc (_S_debug_messages): Add as comment
> the _Debug_msg_id
> entry associated to the array entry.
These comments are a great idea, thanks.
If you agree with the _Unchecked name, OK to commit with that change.
next prev parent reply other threads:[~2023-01-23 9:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-23 6:02 François Dumont
2023-01-23 9:22 ` Jonathan Wakely [this message]
2023-01-23 18:15 ` François Dumont
2023-01-23 18:25 ` 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='CACb0b4=2yVEUK_2i0nDgdbhQktvzvcRHqma0TeMQ5Nhva7=Zag@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).