Re: [boost] [move] unique_ptr converting constructor

Ion Gaztañaga wrote:

That's because the converting constructor is programed as taking rv> (similar to unique_ptr &&) and that provokes emulation limitations when returning by value convertible types.

Yes. I tried to give it the result of boost::move, which should be rv<>, but it still didn't work. By value has its own limitations, as described. This aside, ought not unique_ptr and make_unique be in boost instead of movelib? I'll remove boost::make_unique if we do this.