public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/115420] Default constructor of unordered_map deleted Date: Thu, 13 Jun 2024 13:10:39 +0000 [thread overview] Message-ID: <bug-115420-4-Ut1GEmbBV7@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-115420-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115420 --- Comment #7 from GCC Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Jonathan Wakely <redi@gcc.gnu.org>: https://gcc.gnu.org/g:cc38bdf093c44918edff819ae6c73d03c726b341 commit r15-1256-gcc38bdf093c44918edff819ae6c73d03c726b341 Author: Jonathan Wakely <jwakely@redhat.com> Date: Tue Jun 11 11:08:12 2024 +0100 libstdc++: Improve diagnostics for invalid std::hash specializations [PR115420] When using a key type without a valid std::hash specialization the unordered containers give confusing diagnostics about the default constructor being deleted. Add a static_assert that will fail for disabled std::hash specializations (and for a subset of custom hash functions). libstdc++-v3/ChangeLog: PR libstdc++/115420 * include/bits/hashtable.h (_Hashtable): Add static_assert to check that hash function is copy constructible. * testsuite/23_containers/unordered_map/115420.cc: New test.
next prev parent reply other threads:[~2024-06-13 13:10 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-06-10 17:20 [Bug c++/115420] New: " krebbel at gcc dot gnu.org 2024-06-10 17:23 ` [Bug libstdc++/115420] " pinskia at gcc dot gnu.org 2024-06-11 5:46 ` krebbel at gcc dot gnu.org 2024-06-11 5:47 ` krebbel at gcc dot gnu.org 2024-06-11 7:08 ` xry111 at gcc dot gnu.org 2024-06-11 9:41 ` redi at gcc dot gnu.org 2024-06-11 9:44 ` redi at gcc dot gnu.org 2024-06-11 9:55 ` redi at gcc dot gnu.org 2024-06-13 13:10 ` cvs-commit at gcc dot gnu.org [this message] 2024-06-13 13:14 ` redi at gcc dot gnu.org 2024-06-25 10:59 ` 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-115420-4-Ut1GEmbBV7@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: linkBe 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).