public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/54835] [C++11] Explicit default constructors not respected during copy-list-initialization
Date: Fri, 15 Feb 2013 20:56:00 -0000	[thread overview]
Message-ID: <bug-54835-4-YcS1lq4bwO@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-54835-4@http.gcc.gnu.org/bugzilla/>


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

Jason Merrill <jason at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jason at gcc dot gnu.org

--- Comment #2 from Jason Merrill <jason at gcc dot gnu.org> 2013-02-15 20:56:04 UTC ---
It's not clear to me that [over.match.list] applies to this initialization,
since the value-initialization bullet is separate from the bullet that
cross-references [over.match.list].  And in fact there's code in
convert_like_real specifically to avoid this diagnostic because of this
difference, and it's tested for in initlist40.C.

I'm not opposed to this behavior, but I think it would be a language change.


  parent reply	other threads:[~2013-02-15 20:56 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-06 11:20 [Bug c++/54835] New: " daniel.kruegler at googlemail dot com
2013-01-24 13:32 ` [Bug c++/54835] " redi at gcc dot gnu.org
2013-02-15 20:56 ` jason at gcc dot gnu.org [this message]
2013-02-16 11:57 ` daniel.kruegler at googlemail dot com
2013-02-16 15:02 ` [Bug c++/54835] [C++11][DR 1518] " jason at gcc dot gnu.org
2013-03-17  2:37 ` jason at gcc dot gnu.org
2013-03-23  5:11 ` jason at gcc dot gnu.org
2013-03-23  5:12 ` jason at gcc dot gnu.org
2013-09-12  8:44 ` redi at gcc dot gnu.org
2015-05-04 15:29 ` jason at gcc dot gnu.org
2015-05-04 18:35 ` daniel.kruegler at googlemail dot com
2015-05-06  2:08 ` jason at gcc dot gnu.org
2015-05-06 18:09 ` jason at gcc dot gnu.org
2015-06-15 16:03 ` jason at gcc dot gnu.org
2015-06-15 16:03 ` jason at gcc dot gnu.org
2015-10-24  2:58 ` jason at gcc dot gnu.org
2015-10-24  3:00 ` jason at gcc dot gnu.org
2021-05-11 10:38 ` davveston at gmail dot com
2021-05-11 11:25 ` redi at gcc dot gnu.org
2021-06-07  5:30 ` rs2740 at gmail dot com
2021-06-09 10:20 ` davveston at gmail dot com

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-54835-4-YcS1lq4bwO@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).