public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/106275] unordered_map with std::string key, std::hash<std::string>, and custom equality predicate weirdness
Date: Tue, 12 Jul 2022 22:53:16 +0000 [thread overview]
Message-ID: <bug-106275-4-KHd4svQB60@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106275-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106275
--- Comment #4 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Jonathan Wakely from comment #3)
> The __is_fast_hash trait is true for std::hash<std::string> but false for
> your custom hash function.
Oops, I mean the other way around! std::hash<std::string> is considered slow,
your custom hash function is not.
next prev parent reply other threads:[~2022-07-12 22:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-12 22:18 [Bug libstdc++/106275] New: " cuzdav at gmail dot com
2022-07-12 22:19 ` [Bug libstdc++/106275] " cuzdav at gmail dot com
2022-07-12 22:49 ` redi at gcc dot gnu.org
2022-07-12 22:51 ` redi at gcc dot gnu.org
2022-07-12 22:53 ` redi at gcc dot gnu.org [this message]
2022-07-12 23:00 ` redi at gcc dot gnu.org
2022-07-13 16:28 ` cuzdav at gmail dot com
2022-07-13 20:14 ` redi at gcc dot gnu.org
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=bug-106275-4-KHd4svQB60@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).