anchor.diff:  
   There is no Java method to determine whether an arbitrary collection
   is mutable or immutable, so it is not possible in Clojure to implement
  -`EGAL`'s intended behavior, although one might consider `=` "closer"
  +the intended behavior of `EGAL`, although one might consider `=` "closer"
   to `EGAL` if it always returned `false` when one of the arguments was
   a non-Clojure collection.
   
   === Lazy and pending values
   
   Baker recommends that `EGAL` force lazy values when comparing them
  -(see Section 3. J. "Lazy Values").  When comparing a lazy sequence to
  +(see Section 3. J. "Lazy Values" in the "Equal Rights for Functional Objects" paper).  When comparing a lazy sequence to
   another sequential thing, Clojure's `=` does force the evaluation of
   the lazy sequence, stopping if it reaches a non-`=` sequence element.
   Chunked sequences, e.g. as produced by `range`, can cause evaluation
  
positive.code: 
  This document discusses the concept of equality in Clojure, including the functions `=`, `==`, and `identical?`, and how they differ from Java's `equals` method.  It also has some description of Clojure's `hash`, and how it differs from Java's `hashCode`. The beginning of this guide provides a summary of the most important information for quick reference followed by a much more extensive review of the details.
  
  _Information in this guide describes the behavior of Clojure 1.9.0 unless noted otherwise._
  
  == Summary
  
  
negative.code: false
  ----
  
  If you want to test for numeric equality across different numeric categories, use `==`.  See the section <<xref/../equality#numbers,Numbers>> below for details.
  
  Sequential collections (sequences, vectors, lists, and queues) with equal elements in the same order are equal:
  
  