An &own reference seems like it would just be equivalent to a Box.

Box heap allocates, references do not.

> `&own` references that take ownership of the object and free it when the reference goes out of scope

How can you free something if it's not allocated

	▲	steveklabnik 4 days ago \| parent [-]
		Sorry, yeah that phrasing was bad: I kinda think an "owning reference" is a contradiction in terms but I didn't come up with the idea. What I meant was, creating a box creates a new allocation, whereas my understanding of &own would take over an existing allocation.