The text I quoted seemed to suggest that the reference going out of scope could trigger deallocation.
Re:What's a reference in Rust?
by Manishearth on Wednesday November 29, 2017 @05:31PM
(#15811522)
Which is true.
The word "reference" is overloaded, it can be used to mean "anything pointery that's guaranteed to exist" too. Box<T> in this context is a reference.
The post does kind of dance between definitions of "reference" a bit, but I think that's intentional.
The trick is that if it is (possibly) returned from a function, it is moved instead of dropped.
It's also important to distinguish Box from Rc. Both are heap values but have very different behavior.