It's not a feature of Rust; it's a "feature" of the way we design operating systems and processors. This is the same in C.

The same could happen in C++, I think. Destructors are supposed to be called recursively.

1) he should pass by reference to avoid the extra copy. So in his example yes it’s dev naivety

2) but somewhere somehow this object will deallocate, so his trick of putting it to another thread would work if the deal location takes awhile. Same for cpp if you have a massive object in a unique ptr. So it’s not a rust issue