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][_Hashtable] Fix insertion of range of type convertible to value_type PR 105714
Date: Tue, 14 Jun 2022 22:53:01 +0100 [thread overview]
Message-ID: <CACb0b4=gcj_02W58=5LdsjthKfXm9W3Zj9SepbqH4K_FWUSJYA@mail.gmail.com> (raw)
In-Reply-To: <fa10777a-0d31-ba0d-216d-96c03139a7c0@gmail.com>
On Wed, 25 May 2022 at 06:10, François Dumont <frs.dumont@gmail.com> wrote:
>
> Here is the patch to fix just what is described in PR 105714.
>
> libstdc++: [_Hashtable] Insert range of types convertible to
> value_type PR 105714
>
> Fix insertion of range of types convertible to value_type.
>
> libstdc++-v3/ChangeLog:
>
> PR libstdc++/105714
> * include/bits/hashtable_policy.h (_ValueTypeEnforcer): New.
> * include/bits/hashtable.h
> (_Hashtable<>::_M_insert_unique_aux): New.
> (_Hashtable<>::_M_insert(_Arg&&, const _NodeGenerator&,
> true_type)): Use latters.
> (_Hashtable<>::_M_insert(_Arg&&, const _NodeGenerator&,
> false_type)): Likewise.
> (_Hashtable(_InputIterator, _InputIterator, size_type,
> const _Hash&, const _Equal&,
> const allocator_type&, true_type)): Use this.insert range.
> (_Hashtable(_InputIterator, _InputIterator, size_type,
> const _Hash&, const _Equal&,
> const allocator_type&, false_type)): Use _M_insert.
> * testsuite/23_containers/unordered_map/cons/56112.cc:
> Check how many times conversion
> is done.
> * testsuite/23_containers/unordered_map/insert/105714.cc:
> New test.
> * testsuite/23_containers/unordered_set/insert/105714.cc:
> New test.
>
> Tested under Linux x64, ok to commit ?
I think "_ConvertToValueType" would be a better name than
_ValueTypeEnforcer, and all overloads of _ValueTypeEnforcer can be
const.
OK with that change, thanks.
next prev parent reply other threads:[~2022-06-14 21:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-15 9:05 [PATCH][_Hashtable] Fix insertion of range of type convertible to value_type PR 56112 François Dumont
2022-02-21 17:59 ` François Dumont
2022-02-21 20:54 ` Jonathan Wakely
2022-02-21 21:33 ` François Dumont
2022-05-05 17:37 ` François Dumont
2022-05-11 17:03 ` François Dumont
2022-05-18 17:39 ` François Dumont
2022-05-24 10:18 ` Jonathan Wakely
2022-05-24 10:22 ` Jonathan Wakely
2022-05-24 10:31 ` Jonathan Wakely
2022-05-25 5:09 ` [PATCH][_Hashtable] Fix insertion of range of type convertible to value_type PR 105714 François Dumont
2022-06-07 19:50 ` François Dumont
2022-06-14 21:53 ` Jonathan Wakely [this message]
2022-05-24 20:25 ` [PATCH][_Hashtable] Fix insertion of range of type convertible to value_type PR 56112 François Dumont
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=gcj_02W58=5LdsjthKfXm9W3Zj9SepbqH4K_FWUSJYA@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).