public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "coppro at users dot sourceforge.net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/49205] Default constructor with pack expansion parameter not detected
Date: Sat, 28 May 2011 01:46:00 -0000	[thread overview]
Message-ID: <bug-49205-4-3zeQV2dqjj@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-49205-4@http.gcc.gnu.org/bugzilla/>

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

Sean Hunt <coppro at users dot sourceforge.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |coppro at users dot
                   |                            |sourceforge.net

--- Comment #1 from Sean Hunt <coppro at users dot sourceforge.net> 2011-05-28 00:58:28 UTC ---
While this behavior is erroneous, consensus at clang was that WG21 made an
oversight in allowing this. Template constructors are banned from being copy or
move constructors, and historically this prohibition was not necessary for
default constructors since there was no special handling of them except when
implicit.


  reply	other threads:[~2011-05-28  0:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-28  0:48 [Bug c++/49205] New: " schaub.johannes at googlemail dot com
2011-05-28  1:46 ` coppro at users dot sourceforge.net [this message]
2011-05-28  1:55 ` [Bug c++/49205] [C++0x] " schaub.johannes at googlemail dot com
2011-05-28  2:06 ` scshunt at csclub dot uwaterloo.ca
2011-05-28  3:22 ` schaub.johannes at googlemail dot com
2011-06-20  1:53 ` jason at gcc dot gnu.org
2011-06-20 14:41 ` jason at gcc dot gnu.org
2011-06-20 14:46 ` jason at gcc dot gnu.org
2011-06-20 15:57 ` schaub.johannes at googlemail 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-49205-4-3zeQV2dqjj@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).