> don't use move on an object that's doing RIAA to take and release a lock. Absolutely. If the question is "what would I do in C++ today" then my answer is tha

> don't use move on an object that's doing RIAA to take and release a lock. Absolutely. If the question is "what would I do in C++ today" then my answer is that I would use RAII subject to common-sense rules like this. > Explicitly disable those actions (private copy constructor and operator, private move) That's a decent enough solution within the context of C++ as an unchangeable thing, but I want people to look beyond that context. C++ has never been an unchangeable thing. Programmers shouldn't have to take such extra steps, so closely tied to how the language works that year, to get a conceptually simple result. That's how bugs creep in, and how even correct code becomes drudgery. We have no choice but to accept it now, but we shouldn't accept it permanently.