== operators are a great source of confusion in the languages where they are prevalent. People coming from languages without it expect
== to mean deep equality, and people coming from languages with
=== to be deep equality and
== to mean equality after some type coercion. See #1749.
Throughout the standard library, as far as I’m aware,
== both take the same action. However, the presence of both encourages 3rd party library developers to create unintuitive “sloppy equals” operator overloads, especially when translating from ruby.
I think that cases where
=== differ, if they exist, should be removed, along with the ambiguity the operator creates.