anchor.diff:  
   == Defining equality for your own types
   
  -See these for examples on how to do this, and much more.  In
  +See the code of the projects below for examples of how to do this, and much more.  In
   particular, the Java methods `equals` and `hashCode` from standard
   Java objects, and the Clojure Java methods `equiv` and `hasheq` are
   the most relevant for how `=` and `hash` behave.
   
   * https://github.com/clojure/data.priority-map[org.clojure/data.priority-map]
  -  but note that it needs a change to implement `hash` consistently
  -  with `=`.
  -  https://dev.clojure.org/jira/browse/DPRIMAP-12[DPRIMAP-12]
  -* https://github.com/amalloy/ordered[org.flatland/ordered] but note
  +* https://github.com/clj-commons/ordered[org.flatland/ordered] but note
     that it needs a change so that its custom ordered map data structure
     is not `=` to any Clojure record:
  -  https://github.com/amalloy/ordered/pull/34[PR #34]
  +  https://github.com/clj-commons/ordered/pull/34[PR #34]
   
   == References
   
  
positive.code: when comparing
  https://en.wikipedia.org/wiki/Closure_(computer_programming)[closures]
  to each other (see Section 3. D. "Equality of Functions and
  Function-Closures").
  
  When given a function or closure as an argument, Clojure's `=` only
  returns `true` if they are `identical?` to each other.
  
negative.code: * When comparing collections with `=`, numbers within the collections
    are also compared with `=`, so the three numeric categories above
    are significant.
  * 'Not a Number' values `pass:[##NaN]`, `Float/NaN`, and `Double/NaN` are not
    `=` or `==` to anything, not even themselves.
    _Recommendation:_ Avoid including `pass:[##NaN]` inside of Clojure data
    structures where you want to compare them to each other using `=`,
    and sometimes get `true` as the result.
  * 0.0 is `=` to -0.0
  