Re: [boost] [shared_ptr] dangerous implementation of moveconstructor

Ion Gaztañaga wrote:

Ok. So if such objects can't be moved, there is no problem to offer reusability for other objects that can be moved ;-)

Reusability was never questioned. Usability after move is the problem. The question is whether the user may legitimately do something with an moved-from object with predictable results _except_ destroying or reusing it via assignment or reset.