Challenge 3: Why a Reference Cannot Be Null, Tied to What It Actually Is — Possible Solution
====================================================================

Per the chapter, a reference is an ALIAS for an existing variable --
it is not a separate object that happens to hold an address the way a
pointer is; it's simply another name for a piece of memory that
already, genuinely exists. "Null" is a concept that only makes sense
for something that CAN independently point at "nothing" -- a pointer
is a real, distinct variable whose own value is an address, and that
value can meaningfully be set to a special "points at nothing" sentinel
(NULL), because the pointer's identity and the thing it points to are
two separate concerns.

A reference has no such separate identity to hold a "points at
nothing" value in the first place. When int &ref = x; is declared, ref
doesn't get its OWN storage holding "the address of x" that could
instead hold "no address at all" -- ref simply becomes another name
FOR x itself. There is no independent "reference object" sitting
between the name ref and the variable x that could be pointed
elsewhere, or nowhere -- asking "what does ref refer to, if not to
something?" doesn't have a coherent answer, because a reference's
entire nature is inseparable from referring to something specific,
decided permanently the moment it's created.

This is exactly why the chapter states a reference must be initialized
immediately, and can never be rebound: both rules follow directly from
references being aliases rather than independent objects. A pointer's
"null" state and reassignability both stem from a pointer being its
own separate thing with its own address-shaped value; a reference has
neither property precisely because it never was its own separate
thing to begin with.

WHY THIS WORKS AS AN ANSWER
------------------------------
This grounds the "no null" property in the specific definition the
chapter gives (a reference is an alias, not a separate object) rather
than treating it as an arbitrary language rule, and explicitly connects
it to the other two reference constraints (must-initialize-immediately,
cannot-rebind) as following from the SAME underlying reason rather than
being three unrelated facts.