> On Oct 17, 2017, at 7:52 PM, Kevin Nattinger via swift-evolution
> <swift-evolution@swift.org> wrote:
>
> So, what I'm getting from this explanation is that `Equatable` is meaningless
> on its own; each class needs to document exactly what "substitutability"
> means as implemented, and any code that uses `==` needs to check the
> documentation for that specific class and make sure the intended use
> ("context," as you say) aligns with the class's definition.
This is how it works in every language I’ve ever worked on that has a concept
of overridable equality checks, including Objective-C.
_______________________________________________
swift-evolution mailing list
swift-evolution@swift.org
https://lists.swift.org/mailman/listinfo/swift-evolution
