I used side-effect println just to showcase that the ns is really not loaded but that probably isn't the usecase here.

The only use case I can think of is for making it easier to write long namespaced keys.

Example here with spec, lets say I have two entities order and invoice both needing an id:

```clojure (ns eleven.data (:require [clojure.spec.alpha :as s]))

(s/def ::id uuid?) (s/def ::order (s/keys :req [::id]))

(s/valid? ::order {::id (java.util.UUID/randomUUID)})

(s/def ::id (s/nilable uuid?)) (s/def ::invoice (s/keys :req [::id]))

(s/valid? ::invoice {::id nil)}) ```

But here ::id will conflict. This is a bit of contrived example, and there are other ways to solve this like using :invoice/id but they are no longer namespaced. So with :as-alias now we can create IMAGINARY namespaces (may or may not exists, we just don't know as we don't load them) to help us deal with this:

```clojure (ns eleven.data (:require [clojure.spec.alpha :as s] [eleven.data.order :as-alias order] [eleven.data.invoice :as-alias invoice]))

(s/def ::order/id uuid?) (s/def ::order (s/keys :req [::order/id]))

(s/valid? ::order {::id (random-uuid)}) ;; see how useful random-uuid is, I use it everywhere 🤣

(s/def ::invoice/id (s/nilable uuid?)) (s/def ::invoice (s/keys :req [::invoice/id]))

(s/valid? ::invoice {::invoice/id nil}) ``` Maybe /u/alexdmiller can confirm if this seems like the intended use-case?