> I view move semantics as not a memory safety thing at all (in fact, use-after-move can be exactly as ugly as use-after-delete), Note that move-destructors we

> I view move semantics as not a memory safety thing at all (in fact, use-after-move can be exactly as ugly as use-after-delete), Note that move-destructors were also considered for C++11, and were not added for lack of time / implementation experience . And this is really too bad, because they are at least as important as move constructors if not more so; I've yet to encounter a case where you actually want to use a moved-from object after the move.