This is the mail archive of the libstdc++@gcc.gnu.org mailing list for the libstdc++ project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: rvalue references in libstdc++

From: "Peter Dimov" <pdimov at mmltd dot net>
To: "Howard Hinnant" <hhinnant at apple dot com>, "libstdc++" <libstdc++ at gcc dot gnu dot org>, "Chris Jefferson" <chris at bubblescope dot net>
Date: Tue, 1 May 2007 00:18:08 +0300
Subject: Re: rvalue references in libstdc++
References: <5cc6b04e0704301311i2a0f196fx7464bbdf8d9eca71@mail.gmail.com> <6ECF4C2A-8E8A-4D6D-BF1A-C999A2C9CEC2@apple.com>

Howard Hinnant wrote:

When faced with this same challenge in the CodeWarrior library I had
good luck with the technique outlined here:
http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2005/n1771.html#old_move

I was going to suggest the same thing... but why the second overload of move? There is no use case where the argument is an rvalue, right?

Follow-Ups:
- Re: rvalue references in libstdc++
  - From: Howard Hinnant

References:
- rvalue references in libstdc++
  - From: Chris Jefferson
- Re: rvalue references in libstdc++
  - From: Howard Hinnant

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]