public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "bmerry at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/59167] New: Add a specialization for std::hash<__gnu_debug::string> Date: Mon, 18 Nov 2013 08:26:00 -0000 [thread overview] Message-ID: <bug-59167-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59167 Bug ID: 59167 Summary: Add a specialization for std::hash<__gnu_debug::string> Product: gcc Version: 4.8.1 Status: UNCONFIRMED Severity: enhancement Priority: P3 Component: libstdc++ Assignee: unassigned at gcc dot gnu.org Reporter: bmerry at gmail dot com I have code for which I am explicitly selecting debug containers from the __gnu_debug namespace (I'm not using -D_GLIBCXX_DEBUG since it breaks the ABI with Boost and I don't want to require people to rebuild Boost to use a debug build of my code). This mostly works, but when I try to use an unordered_map with __gnu_debug::string as the key type I get errors because std::hash hasn't been specialized for it. I can write my own specialization, but it would be nice if the library just provided it. Obviously the other variants (wstring, u16string, u32string should be handled too).
next reply other threads:[~2013-11-18 8:26 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-11-18 8:26 bmerry at gmail dot com [this message] 2015-04-09 15:04 ` [Bug libstdc++/59167] " 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-59167-4@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).