The equivalent of the C++ move in Rust are the function take/replace (like mem::replace ajd option::take). And it is fully memory safe. You can build all the

The equivalent of the C++ move in Rust are the function take/replace (like mem::replace ajd option::take). And it is fully memory safe. You can build all the ownership you want by using raw pointers in Rust. And there is nothing wrong with a specific problem requiring unsafe because the problem cannot be taught to the borrow checker. But there is a point in your stack of abstractions where you can expose a safe and ergonomic API. If you have a concrete example I would love to get a crack at it.