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] Avoid allocator operator== in _Safe_container
Date: Mon, 9 Aug 2021 11:33:24 +0100 [thread overview]
Message-ID: <CACb0b4=G0V4dUCZUKRFpu0G4yJ5sUNDfyvLb1PQn8uq=s-iXMQ@mail.gmail.com> (raw)
In-Reply-To: <6edc763b-e463-a676-0232-7b2193fb403b@gmail.com>
On Mon, 9 Aug 2021 at 11:26, François Dumont via Libstdc++
<libstdc++@gcc.gnu.org> wrote:
>
> Some newly introduced tests in
> 23_containers/unordered_map/cons/default.cc revealed that we are forcing
> the allocator type to have a operator==.
All allocators are required to have operator== so that should not be a
problem. What is the error?
next prev parent reply other threads:[~2021-08-09 10:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-09 10:23 François Dumont
2021-08-09 10:33 ` Jonathan Wakely [this message]
2021-08-09 10:34 ` Jonathan Wakely
2021-08-09 10:45 ` Jonathan Wakely
2021-08-09 11:52 ` François Dumont
2021-08-09 12:08 ` François Dumont
2021-08-09 14:24 ` 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=G0V4dUCZUKRFpu0G4yJ5sUNDfyvLb1PQn8uq=s-iXMQ@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).