clang-tidy has a check for this. https://clang.llvm.org/extra/clang-tidy/checks/bugprone/use-...

MSVC and the Clang static analyzer have a analysis checks for this too. Not sure about GCC.

It's worth remembering though that values can be reinitialized in C++, after move.

I think you missed my point. The problem is not lack of guarding against programmer mistakes. It's that the compiler generates unnecessary code.