Re: [boost] [move] [range] move algorithm (was: interest: the pass-by-value...)

Krzysztof Czainski wrote:

2014-02-15 23:17 GMT+01:00 Adam Wulkiewicz :

...

Krzysztof Czainski wrote:

...

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'.

AFAIR the naming of adaptors was always a concern. But just look at the reference: http://www.boost.org/doc/libs/1_55_0/libs/range/doc/html/range/reference/ada.... There is reversed, transformed, copied, etc. Maybe a little bit misleading but in the case of Boost.Range it doesn't mean that the range was changed somehow. Regards, Adam