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] Enhance std::erase_if for vector/deque
Date: Wed, 8 Dec 2021 16:17:39 +0000 [thread overview]
Message-ID: <CACb0b4=7DrYpk42cY07cfwcyn+hBKo5LwOqtkRdG+JtwVD2p4w@mail.gmail.com> (raw)
In-Reply-To: <260f7bad-9d35-44ea-a354-ad88dd04b685@gmail.com>
On Sun, 21 Nov 2021 at 11:26, François Dumont via Libstdc++
<libstdc++@gcc.gnu.org> wrote:
>
> I tried to use the same approach I used for node based containers but
> got ambiguity on erase calls. I think this simple version will do the work.
>
> libstdc++: [_GLIBCXX_DEBUG] Enhance std::erase_if for vector/deque
>
> libstdc++-v3/ChangeLog:
>
> * include/std/deque (erase_if): Use _GLIBCXX_STD_C
> container reference and
> __niter_wrap to limit _GLIBCXX_DEBUG mode impact.
> * include/std/vector (erase_if): Likewise.
>
> Tested under Linux x86_64 normal and _GLIBCXX_DEBUG modes.
>
> Ok to commit ?
OK, thanks.
prev parent reply other threads:[~2021-12-08 16:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-21 11:24 François Dumont
2021-12-08 16:17 ` Jonathan Wakely [this message]
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=7DrYpk42cY07cfwcyn+hBKo5LwOqtkRdG+JtwVD2p4w@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).