e> is a descendant of <code>x</code>. Note
that this is an inclusive relationship: <code>x</code> is a descendant and ancestor of
itself.</p>

<p>We can then define references as simply <em>names</em> for paths. When you create a
reference, you&#39;re declaring that an ownership path exists to this address
of memory.</p>

<p>Tragically, plenty of data doesn&#39;t reside on the stack, and we must also
accommodate this. Globals and thread-locals are simple enough to model as
residing at the bottom of the stac