On 29/08/2018 20:51, Andrey Semashev wrote:
On 08/29/18 04:00, Gavin Lambert wrote:
On 29/08/2018 01:09, Andrey Semashev wrote:
For example, if I'm currently using Boost.Move or boost::shared_ptr, does this mean I have to port my code to native rvalue references and std::shared_ptr?
AFAIK, migrating from Boost.Move to native references is largely invisible to external C++11 consumers, so as a maintainer you could decide to leave the existing code (for reduced churn) or replace it (for code simplicity), mostly at your own whim or even piecemeal.
It is almost invisible for users, but it's not for maintainers. Like I said, if I want to keep my code base consistent (and I do) I would have to perform the full transition.
That is what I said. Although some people might prefer to keep BOOST_MOVABLE_BUT_NOT_COPYABLE and BOOST_COPYABLE_AND_MOVABLE, which are nicely descriptive; unlike most of the other macros, which are just cruft when you know you're using C++11.