anchor.diff:  
   == Contributing
   
  -Clojure and ClojureScript share the same http://clojure.org/contributing[Contributor Agreement and development process].+Clojure and ClojureScript share the same http://clojure.org/contributing[Contributor Agreement and development process].
  
positive.code: 
  * You must currently use the `ns` form only with the following caveats
  ** You must use the `:only` form of `:use`
  ** `:require` supports `:as` and `:refer`
  *** both options can be skipped
  *** in this case a symbol can be used as a libspec directly
  **** * that is, `(:require lib.foo)` and `(:require [lib.foo])` are both supported and mean the same thing
  *** http://clojure.github.io/clojure/clojure.core-api.html#clojure.core/require[prefix lists] are not supported
  ** The only option for `:refer-clojure` is `:exclude`
  ** `:import` is available only for importing Google Closure classes
  *** ClojureScript types and records should be brought in with `:use` or `:require :refer`, not `:import`ed
  * Macros must be defined in a different _compilation stage_ than the one from 
  where they are consumed. One way to achieve this is to define them in one namespace and use them from another. They are referenced via the `:require-macros` / `:use-macros` options to `ns`
  ** `:require-macros` and `:use-macros` support the same forms that `:require` and `:use` do
  
  _Implicit macro loading_: If a namespace is required or used, and that namespace _itself_ requires or uses macros from its own namespace, then the macros will be implicitly required or used using the same specifications. This oftentimes leads to simplified library usage, such that the consuming namespace need not be concerned about explicitly distinguishing between whether certain vars are functions or macros.
  
  _Inline macro specification_: As a convenience, `:require` can be given either `:include-macros true` or `:refer-macros
  [syms...]`. Both desugar into forms which explicitly load the matching Clojure file containing macros. (This works independently of whether the namespace being required internally requires or uses its own macros.) For example:
  
negative.code:             [woz.core :as woz :refer [woz-fn]])
    (:require-macros [foo.core :as foo]
                     [woz.core :as woz :refer [apple jax]]))
  ----
  
  _Auto-aliasing clojure namespaces_: If a non-existing `clojure.\*` namespace is required or used and a matching `cljs.*` namespace exists, the `cljs.\*` namespace will be loaded and an alias will be automatically established from the `clojure.*` namespace to the `cljs.*` namespace. For example:
  
  [source,clojure]
  ----
  (ns testme.core (:require [clojure.test]))
  ----
  
  will be automatically converted to
  
  [source,clojure]
  ----
  (ns testme.core (:require [cljs.test :as clojure.test]))
  ----
  
  == Libs
  