public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "david.d.kretzmer at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/51553] brace initialization and conversion operators
Date: Mon, 30 Jun 2014 23:16:00 -0000 [thread overview]
Message-ID: <bug-51553-4-3sVYZG6h8o@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-51553-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=51553
david.d.kretzmer at gmail dot com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |david.d.kretzmer at gmail dot com
--- Comment #4 from david.d.kretzmer at gmail dot com ---
13.3.3.1 p4 [over.best.ics]
[...] or when the initializer
list has exactly one element and a conversion to some class X or reference to
(possibly cv-qualified) X is
considered for the first parameter of a constructor of X, or by 13.3.1.4,
13.3.1.5, or 13.3.1.6 in all cases, only
standard conversion sequences and ellipsis conversion sequences are considered.
If I understand this correctly then the behavior before gcc 4.7 was actually
correct: only standard conversions are considered, conversion functions are
not.
next prev parent reply other threads:[~2014-06-30 23:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-14 20:07 [Bug c++/51553] New: " dave at boostpro dot com
2011-12-19 16:41 ` [Bug c++/51553] " jason at gcc dot gnu.org
2011-12-19 20:13 ` jason at gcc dot gnu.org
2011-12-19 20:17 ` jason at gcc dot gnu.org
2011-12-19 20:19 ` jason at gcc dot gnu.org
2014-06-30 23:16 ` david.d.kretzmer at gmail dot com [this message]
2014-07-01 10:00 ` redi at gcc dot gnu.org
2014-07-01 11:03 ` david.d.kretzmer at gmail dot com
2015-10-17 14:14 ` 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-51553-4-3sVYZG6h8o@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).