anchor.diff:  This example imports the `Date` and `UUID` class from the `java.util` package and the `File` class from the `java.io` package.
   
   
  -
  -
  
positive.code: 
  * `clojure.set` - just loads `clojure.set` namespace (if not already loaded)
  * `[clojure.set :as set]` - load and create an alias `set` for the namespace `clojure.set`
  ** This allows you to refer to vars in set with for example `set/union` instead of `clojure.set/union`
  * `[clojure.set :refer [union intersection]]` - load and refer specific vars into this namespace
  ** This allows you to use just `union` instead of `clojure.set/union`
  
  
negative.code: 
  Thus the namespace name `com.some-example.my-app` becomes the load path `com/some_example/my_app.clj`. Load paths are searched using the JVM classpath. The classpath is a series of directory locations or JAR files (JARs are essentially just zip files). 
  
  When a resource is needed, the JVM searches each classpath location in order for a file at the relative location of the load path. So if the classpath was `src:test`, the load path would be checked at `src/com/some_example/my_app.clj` then `test/com/some_example/my_app.clj`.
  
  There are several ways to load code in Clojure, but most commonly loading is accomplished via `require`.
  
  Due to this loading convention, most Clojure is structured with a 1-to-1 mapping of namespaces to files, stored in hierarchical fashion that maps to the namespace structure.
  
  