From: Florian Weimer <fweimer@redhat.com>
To: brian.budge@gmail.com
Cc: gcc-help@gcc.gnu.org
Subject: Re: potential bug regarding rvalue refs?
Date: Wed, 29 Jan 2014 19:40:00 -0000 [thread overview]
Message-ID: <52E9591E.2000609@redhat.com> (raw)
In-Reply-To: <CANjXV6_d5pSxtRzFh8urwuEq-VPft=3THkGxgCD+wNL6rP8Q7Q@mail.gmail.com>
On 01/29/2014 07:58 PM, Brian Budge wrote:
> f_impl(std::forward<foo>(t));
You need to write std::forward<T> instead of std::forward<foo> to get
the expected forwarding behavior.
> Although I'm far from an expert with rvalue refs and universal refs,
> this seems like a bug to me. Thoughts?
What output do you expected instead?
--
Florian Weimer / Red Hat Product Security Team
next prev parent reply other threads:[~2014-01-29 19:40 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 [this message]
2014-01-29 20:10 ` Jonathan Wakely
2014-01-29 20:56 ` Brian Budge
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=52E9591E.2000609@redhat.com \
--to=fweimer@redhat.com \
--cc=brian.budge@gmail.com \
--cc=gcc-help@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).