public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "paolo.carlini at oracle dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/56267] [4.7/4.8 Regression] unordered containers require Assignable hash function
Date: Sun, 10 Feb 2013 23:00:00 -0000	[thread overview]
Message-ID: <bug-56267-4-vWKSFkXhJU@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-56267-4@http.gcc.gnu.org/bugzilla/>


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56267

--- Comment #2 from Paolo Carlini <paolo.carlini at oracle dot com> 2013-02-10 23:00:34 UTC ---
Thanks Jon for fully handling this. I understand that in principle we could
have checked is_nothrow_default_constructible, but it's of course much better
if we can just use operations guaranteed by the Standard and be done with it.
If you remember, the is_default_constructible check made me a little nervous
from the start...


  parent reply	other threads:[~2013-02-10 23:00 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-09 18:50 [Bug libstdc++/56267] New: " redi at gcc dot gnu.org
2013-02-10 12:20 ` [Bug libstdc++/56267] " rguenth at gcc dot gnu.org
2013-02-10 21:57 ` redi at gcc dot gnu.org
2013-02-10 23:00 ` paolo.carlini at oracle dot com [this message]
2013-02-11  0:20 ` redi at gcc dot gnu.org
2013-02-11  0:25 ` redi at gcc dot gnu.org
2013-02-14 22:04 ` jsm28 at gcc dot gnu.org
2013-04-11  8:00 ` [Bug libstdc++/56267] [4.7/4.8/4.9 " rguenth at gcc dot gnu.org
2014-01-20 15:50 ` redi at gcc dot gnu.org
2014-01-20 18:50 ` redi at gcc dot gnu.org
2014-01-21 19:39 ` 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-56267-4-vWKSFkXhJU@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).