SAM types introduced, 2016: implicit val intEqual: Eq[Int] = (x: Int, y: Int) => x == y (2/8)
Show this thread
An implicit equality typeclass instance, 2015: implicit val intEqual: Eq[Int] = new Eq[Int] { def equal(x: Int, y: Int): Boolean = x == y } (1/8)
-
-
-
Type inference improves, 2017: implicit val intEq: Eq[Int] = (x, y) => x == y (3/8)
Show this thread -
Developers get lazier, 2018: implicit val intEq: Eq[Int] = _ == _ (4/8)
Show this thread -
Some forgotten experiments, 2019: witness intEq: Eq[Int] = _ == _ (5/8)
Show this thread -
We settle on `given`, 2020: given intEq: Eq[Int] = _ == _ (6/8)
Show this thread -
-
New conversation -
-
-
Nice software archaeology! Where does this particular Eq type class come from?
-
I just made it up for the tweet, but essentially it's: trait Eq[T]: def equal(x: T, y: T): Boolean
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.