In an attempt to contain the damage being inflicted on consistency by the
ad hoc equals methods spread around xml, the logic is centralized and
all the xml classes go through the xml.Equality trait. There are two
forms of xml comparison.
In an attempt to contain the damage being inflicted on consistency by the
ad hoc equals methods spread around xml, the logic is centralized and
all the xml classes go through the xml.Equality trait. There are two
forms of xml comparison.
'''def''' strict_==(other: scala.xml.Equality)
This one tries to honor the little things like symmetry and hashCode
contracts. The equals method routes all comparisons through this.
xml_==(other: Any)
This one picks up where strict_== leaves off. It might declare any two
things equal.
As things stood, the logic not only made a mockery of the collections equals contract, but also laid waste to that of case classes.
Among the obstacles to sanity are/were:
Node extends NodeSeq extends Seq[Node] MetaData extends Iterable[MetaData] The hacky "Group" xml node which throws exceptions with wild abandon, so don't get too close Rampant asymmetry and impossible hashCodes Most classes claiming to be equal to "String" if some specific stringification of it was the same. String was never going to return the favor.
- Companion
- class