anchor.diff:  Existing Clojure libs will have to conform to the ClojureScript subset in order to work in ClojureScript.
   
   Additionally, macros in Clojure libs must be compilable as ClojureScript in order to be consumable in
  -self-host / bootstrapped ClojureScript via its `cljs.js/*load-fn*` capability.
  +self-host / bootstrapped ClojureScript via its `cljs.js/\*load-fn*` capability.
   
   == Vars and the Global Environment
   
  
positive.code: == Other Functions
  
  * printing
  ** `*out*` and `*err*` is currently not implemented
  * regex support
  ** ClojureScript https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/RegExp[regular expression support is that of JavaScript]
  * asserts
  ** In JVM ClojureScript it is not possible to dynamically set `*assert*` to false at runtime. Instead the `:elide-asserts` compiler option must be used to effect elision. (On the other hand, in self-hosted ClojureScript `*assert*` behaves identically to Clojure.)
  
  == Data Structures
  
  
negative.code:       
  Sugared and other `ns` variants can be employed in lieu of using the `:require-macros` primitive; see Namespaces below for details.
  
  Macros are written in `\*.clj` or `*.cljc` files and are compiled either as Clojure when 
  using regular ClojureScript or as ClojureScript when using bootstrapped / self-host 
  ClojureScript. One point of note is that the code generated by Clojure-based 
  ClojureScript macros must target the capabilities in ClojureScript.
  