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, 09 Jan 2014 12:55:00 -0000 [thread overview]
Message-ID: <bug-58764-4-USHyTIegnv@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
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|SUSPENDED |ASSIGNED
Assignee|unassigned at gcc dot gnu.org |redi at gcc dot gnu.org
--- Comment #8 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Marc Glisse from comment #5)
> (In reply to Paolo Carlini from comment #4)
> > Ok, let's wait a bit more, possibly until the next meeting,
>
> The next meeting will be too late for 4.9, so that means sticking to what we
> have now.
"What we have now" for most users is what we shipped in all previous releases
up to 4.8, which allows this:
std::vector<int> v = {};
Rejecting that is a pretty serious regression.
The explicitness of the container constructors had already been questioned by
LWG 2193 when we made the change, so I consider it a mistake to make an
breaking change to conform to wording that is potentially defective.
I'm going to restore the previous constructors (so 4.9 will stick with what we
have now) until the DR is resolved one way or another.
next prev parent reply other threads:[~2014-01-09 12:55 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 [this message]
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
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-USHyTIegnv@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).