Maybe std::make_movable would have been a slightly better name, but it's so much simpler to write std::move.
But that misses too much of the semantics. It also implies ownership transfer, even if copied.
thanks to the incredible advances in terms of developer tooling over the last 50 years (i.e. tab-autocompletion) there should be no difference in writing those two.
std::rvalue
Split the difference with std::moveable().
Also signals it doesn't actually move, while remaining just as fast to type.