15 Apr
2013
15 Apr
'13
5:45 p.m.
On Mon, Apr 15, 2013 at 8:58 AM, Steven Watanabe
AMDG
On 04/15/2013 02:19 AM, Antony Polukhin wrote:
This looks like Boost.Move known limitation:
http://www.boost.org/doc/libs/1_53_0/doc/html/move/emulation_limitations.htm...
I'm afraid that this will confuse a lot of people who use Boost.Any... May be it would be better to disable ravlue emulation and use rvalues only in C++11?
Yeah. Adding Boost.Move emulation in existing libraries is probably a bad idea.
Should be almost as good to change Boost.Any's copy assignment operator to accept by value on C++03 and implement as swap, no? And keep the move constructor and move assignment for both C++03 and C++11. C++11 copy assignment would continue to accept by reference-to-const. - Jeff