public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "daniel.kruegler at googlemail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/50929] [C++0x] Wrong function selected for overload with template and rvalue reference Date: Mon, 31 Oct 2011 07:16:00 -0000 [thread overview] Message-ID: <bug-50929-4-jUQPpr43j9@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-50929-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50929 Daniel Krügler <daniel.kruegler at googlemail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |daniel.kruegler at | |googlemail dot com --- Comment #1 from Daniel Krügler <daniel.kruegler at googlemail dot com> 2011-10-31 07:15:48 UTC --- Your expectations are in violation to the standard ;-). The constructor is selected by overload resolution. The non-template constructor A(const A& a) would be preferred, if there would be a perfect match (e.g. if you had an lvalue of type const A), but in your example you have an lvalue of non-const A. The "perfect-forwarding" template constructor deduces to template <> A(A& t) via reference-collapsing, which is a better match for the argument expression a. So, this looks like an invalid issue to me.
next prev parent reply other threads:[~2011-10-31 7:16 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-10-31 5:42 [Bug c++/50929] New: " jarrydb at cse dot unsw.edu.au 2011-10-31 7:16 ` daniel.kruegler at googlemail dot com [this message] 2011-10-31 7:43 ` [Bug c++/50929] " jarrydb at cse dot unsw.edu.au 2011-10-31 8:25 ` daniel.kruegler at googlemail dot com 2011-10-31 10:10 ` jarrydb at cse dot unsw.edu.au 2011-10-31 10:18 ` daniel.kruegler at googlemail dot com 2011-10-31 10:34 ` jarrydb at cse dot unsw.edu.au 2011-10-31 10:41 ` paolo.carlini at oracle dot com 2011-10-31 11:46 ` redi at gcc dot gnu.org 2011-10-31 12:20 ` paolo.carlini at oracle 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-50929-4-jUQPpr43j9@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: 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).