From: Brian Budge <brian.budge@gmail.com>
To: Jonathan Wakely <jwakely.gcc@gmail.com>
Cc: GCC-help <gcc-help@gcc.gnu.org>
Subject: Re: potential bug regarding rvalue refs?
Date: Wed, 29 Jan 2014 20:56:00 -0000 [thread overview]
Message-ID: <CANjXV68xvMvZAB-Oez=s5dtmMszyRirnB51GZ04bbx-U-BLrsQ@mail.gmail.com> (raw)
In-Reply-To: <CAH6eHdTgZUHm6h_g2pkDuuFABt+CjTpzz6m=ZZsSZFzBFQVSWg@mail.gmail.com>
On Wed, Jan 29, 2014 at 12:09 PM, Jonathan Wakely <jwakely.gcc@gmail.com> wrote:
> This is a question about C++ and not specific to G++ so not really
> on-topic on this list.
>
> On 29 January 2014 18:58, Brian Budge wrote:
>>
>> Although I'm far from an expert with rvalue refs and universal refs,
>> this seems like a bug to me. Thoughts?
>
> G++ is correct, you're forwarding 't' as an rvalue, so overload
> resolution chooses the function taking an rvalue reference.
Florian, Jonathan, thanks for the responses.
Brian
prev parent reply other threads:[~2014-01-29 20:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-29 18:58 Brian Budge
2014-01-29 19:40 ` Florian Weimer
2014-01-29 20:10 ` Jonathan Wakely
2014-01-29 20:56 ` Brian Budge [this message]
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='CANjXV68xvMvZAB-Oez=s5dtmMszyRirnB51GZ04bbx-U-BLrsQ@mail.gmail.com' \
--to=brian.budge@gmail.com \
--cc=gcc-help@gcc.gnu.org \
--cc=jwakely.gcc@gmail.com \
/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).