anchor.diff:  
   PostgresSQL treats some numerical operations (like division by zero) that would compute a `NaN` as a numerical error that fails the query. PostgresQL considers `NaN` to be larger than positive infinity, both in comparison and in sort order. This proposal achieves something very similar by evaluating comparisons involving a `NaN` to `null` and by treating both `NaN` and `null` as the largest values in the global sort order.
   
  -This proposal could be extended with an operator for making equivalence accessible beyond use in grouping and `DISTINCT`.
  +This proposal could be extended with an operator for making equivalence accessible beyond use in grouping and `DISTINCT`. This seems desirable due to plain `=` not being reflexive for all values.
   
   == Benefits to this proposal
   
  
positive.code: 
  === Equality ===
  
  Finally, we propose that equality generally must align with comparability.
  
  To achieve this, we clarify the difference between equality and equivalence, by making lists containing `null` values follow the same difference as the `null` values themselves.
  Concretely, we propose to redefine how equality works for lists in Cypher today.
  To determine if two lists `l1` and `l2` are equal, we propose two simple tests, like so
  
  
negative.code: 
      ** In equality, `null = null` is `null`.
      ** In equivalence, used by grouping and `DISTINCT`, instances of `null` are always treated as being the same value.
      ** However, equality treats `null` values differently if they are an element of a list or a map value.
  
  == Proposal
  
  