public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "thiago at kde dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/57064] [clarification requested] Which overload with ref-qualifier should be called? Date: Thu, 25 Apr 2013 00:53:00 -0000 [thread overview] Message-ID: <bug-57064-4-103XqW0pYG@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-57064-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57064 --- Comment #3 from Thiago Macieira <thiago at kde dot org> 2013-04-25 00:53:20 UTC --- One more note. Given: void p(A &); void p(A &&); void f(A &&a) { p(a); } like the member function case, this calls p(A &). It's slightly surprising at first glance, but is a known and documented case. Unlike the member function case, if you do p(std::move(a)); it will call p(A &&).
next prev parent reply other threads:[~2013-04-25 0:53 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-04-25 0:29 [Bug c++/57064] New: " thiago at kde dot org 2013-04-25 0:45 ` [Bug c++/57064] " thiago at kde dot org 2013-04-25 0:45 ` thiago at kde dot org 2013-04-25 0:53 ` thiago at kde dot org [this message] 2013-04-25 6:19 ` glisse at gcc dot gnu.org 2013-04-25 6:34 ` glisse at gcc dot gnu.org 2013-04-25 6:51 ` thiago at kde dot org 2013-04-25 7:13 ` thiago at kde dot org 2013-04-25 7:28 ` glisse at gcc dot gnu.org 2013-04-25 7:34 ` thiago at kde dot org 2013-04-25 14:42 ` jason at gcc dot gnu.org 2013-04-25 17:50 ` jason at gcc dot gnu.org 2013-04-26 5:05 ` glisse at gcc dot gnu.org 2013-04-26 6:16 ` thiago at kde dot org 2013-04-26 8:12 ` redi at gcc dot gnu.org 2013-04-26 13:45 ` thiago at kde dot 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-57064-4-103XqW0pYG@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).