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++/58764] [4.9 Regression] [lwg/2193] error: converting to ‘const std::vector<std::basic_string<char> >’ from initializer list would use explicit constructor
Date: Thu, 23 Jan 2014 10:44:00 -0000	[thread overview]
Message-ID: <bug-58764-4-pQdA6e4wUW@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-58764-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #15 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Marc Glisse from comment #14)
> I guess consistency for the noexcept specification is not as important.

Since those noexcept specs are not required by the standard I'm not too
concerned about it for now. It would be nice to address at some point, so that
debug mode containers take the same code paths for anything that depends on
nothrow specs.

I don't care about profile mode at all ;-)

Thanks for your help and code reviews with this.


      parent reply	other threads:[~2014-01-23 10:44 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-17  8:04 [Bug libstdc++/58764] New: " markus at trippelsdorf dot de
2013-10-17  9:01 ` [Bug libstdc++/58764] [lwg/2193] " paolo.carlini at oracle dot com
2013-10-17 10:24 ` glisse at gcc dot gnu.org
2013-10-17 10:46 ` paolo.carlini at oracle dot com
2013-10-17 11:46 ` glisse at gcc dot gnu.org
2013-10-17 13:01 ` paolo.carlini at oracle dot com
2013-10-30 13:30 ` redi at gcc dot gnu.org
2014-01-07 11:53 ` [Bug libstdc++/58764] [4.9 Regression] " rguenth at gcc dot gnu.org
2014-01-09 12:55 ` redi at gcc dot gnu.org
2014-01-22 19:47 ` redi at gcc dot gnu.org
2014-01-22 23:51 ` redi at gcc dot gnu.org
2014-01-22 23:57 ` redi at gcc dot gnu.org
2014-01-23 10:40 ` glisse at gcc dot gnu.org
2014-01-23 10:44 ` redi at gcc dot gnu.org [this message]

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-58764-4-pQdA6e4wUW@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).