public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "a.pignotti at sssup dot it" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/46246] [C++0x] Move constructor required when passing a temporary by copy, but not actually used Date: Sun, 31 Oct 2010 15:10:00 -0000 [thread overview] Message-ID: <20101031151000.kZYGaNdkScKXD-LE1-5KVVdpPYJHXro1TH1JLGgOH9Q@z> (raw) In-Reply-To: <bug-46246-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46246 --- Comment #6 from Alessandro Pignotti <a.pignotti at sssup dot it> 2010-10-31 15:10:22 UTC --- Please consider the first test case before declaring this bug invalid. I think should be legal to delete the move construtor and still being able to pass temporaries by copy.
next prev parent reply other threads:[~2010-10-31 15:10 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-10-30 16:27 [Bug c++/46246] New: " a.pignotti at sssup dot it 2010-10-30 16:29 ` [Bug c++/46246] " a.pignotti at sssup dot it 2010-10-30 16:31 ` a.pignotti at sssup dot it 2010-10-31 10:01 ` paolo.carlini at oracle dot com 2010-10-31 12:05 ` redi at gcc dot gnu.org 2010-10-31 13:28 ` paolo.carlini at oracle dot com 2010-10-31 15:10 ` a.pignotti at sssup dot it [this message] 2010-11-01 0:15 ` redi at gcc dot gnu.org 2010-11-01 14:17 ` jason 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=20101031151000.kZYGaNdkScKXD-LE1-5KVVdpPYJHXro1TH1JLGgOH9Q@z \ --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: linkBe 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).