25 Jul
2013
25 Jul
'13
2:15 p.m.
25.07.2013 17:44, Antony Polukhin:
So, what do the community think about such optimization?
I thought that was already done :) (however, never relied on it) I think if it is transparent change - then it should be done. If not - then maybe introduce new "move-emulation-aware" swap? P.S. What about one step further? Move-aware algorithms, like std::rotate? What about C++11 algorithm improvements, like return iterator at std::rotate, std::fill_n, like std::partition for Forward iterators/ranges? ( by the way, just reported bug about boost::partition https://svn.boost.org/trac/boost/ticket/8927 ) -- Evgeny Panasyuk