Re: [boost] [move] interest: the pass-by-value and swap idiom, and explicit copy constructors

Subject: Re: [boost] [move] interest: the pass-by-value and swap idiom, and explicit copy constructors
From: Ion Gaztañaga (igaztanaga_at_[hidden])
Date: 2014-02-20 18:16:58

El 20/02/2014 22:37, John M. Dlugosz escribió:
> On 2/14/2014 10:52 AM, Krzysztof Czainski wrote:
>> (boost::copy()), which compliments the protocol for explicitly stating in
>> code, where a move is allowed (std::move() or boost::move());
>
> My recent experience is that the choice of std::move or boost::move
> depends on the destination, not the object itself.  My situation is when
> Boost is built with move emulation but the compiler really does have
> rvalue references.

If the compiler supports rvalue references how is Boost.Move built with 
move emulation? Why is this situation useful for you?

Ion