
16 Feb
2014
16 Feb
'14
9:33 a.m.
2014-02-15 23:17 GMT+01:00 Adam Wulkiewicz
Hi,
Krzysztof Czainski wrote:
2014-02-15 1:05 GMT+01:00 Adam Wulkiewicz
:
Hmm, how about:
boost::copy( range | movable, out_it );
Yes, of course this should also be possible. There is already boost::move_iterator in Boost.Move. To be consistent with the standard we should probably also have boost::move() algorithm and a range adaptor. But the naming scheme for Range adaptors is different, the past tense should be used, right? Hence "moved".
The name 'moved' would misleadingly suggest that something already moved. But then, so does 'move'. Regards, Kris