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

From: Sohail Somani

The rule should be simple:

After moving, the moved object (i.e., the argument to std::move) should be destructible.

Agreed so far.

I don't think being assignable makes sense because that implies that a default constructor is sensible for T.

If T supports operator =, I think it should be possible to assign TO an object of type T that has been moved from. I don't see how this is related to a default constructor.

Thanks for listening (and discussing this very important topic!)

Agreed. -- Martin Bonner Project Leader PI SHURLOK LTD Telephone: +44 1223 441434 / 203894 (direct) Fax: +44 1223 203999 Email: martin.bonner@pi-shurlok.com www.pi-shurlok.com