public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "glisse at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/58764] [lwg/2193] error: converting to ‘const std::vector<std::basic_string<char> >’ from initializer list would use explicit constructor
Date: Thu, 17 Oct 2013 10:24:00 -0000	[thread overview]
Message-ID: <bug-58764-4-KY2ReiTK1V@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 #3 from Marc Glisse <glisse at gcc dot gnu.org> ---
(In reply to Paolo Carlini from comment #2)
> As Marc clarified elsewhere before some patches of him, pre-4.9 we were
> inconsistent about this, thus I understand it could also make sense to
> resolve the inconsistency toward separate default constructor everywhere
> (slightly against the letter of C++11 as-is) or even not resolving it at
> all, leave these bits alone for now and wait for 2193 to be resolved one way
> or another. Maybe Marc has a personal opinion. How many separate default
> constructor we used to have and how many constructors the other way?

Mostly normal mode had separate constructors and debug/profile had merged
constructors.

I am in favor of applying the proposed resolution and having separate
constructors everywhere: I don't care about explicit instantiation of the whole
container class, and it has more functionality. We may want to put a
noexcept(is_nothrow_default_constructible<_Alloc>::value) on the default
constructors, not to lose anything compared to the current code.

I won't write the patch myself.


  parent reply	other threads:[~2013-10-17 10:24 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 [this message]
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

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-KY2ReiTK1V@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).