> but introduced its own puzzles about the validity of the objects after the move. In practice it's really not a puzzle. Most of the time you're using std::mov

> but introduced its own puzzles about the validity of the objects after the move. In practice it's really not a puzzle. Most of the time you're using std::move it's because you don't care about the object you moved from, you're about to drop it on the floor. The other times you either manually reset it or just read the docs of the type to find out what it says the state will be after move. It's not really any different from any other method documentation on a class. unique_ptr (or other unique_* types) are vastly worth it, which did not otherwise have a way to work prior to C++11's move semantics.