Got into yet another argument that Haskell's type classes were superior to Scala's because Haskell has global instance uniqueness. Problem being, as far as I can tell, this is true in theory (by specifications) but not in practice (by implementation): https://nrinaudo.github.io/typeclasses/haskell.html …
-
No, I disagree with that. It’s not at all enforced by default, in practice. That’s just far less of an issue, in practice, than people make it out to be.
In practice, Haskell has global type-class uniqueness. That's not the only reason Haskell type-classes are superior.https://www.youtube.com/watch?v=hIZxTQP1ifo …
-
-
Fair enough - what did I miss in my (nasty) bit of code? Doesn't it expose exactly the fact that global uniqueness is not guaranteed by ghc? Who's got the bigger type class implementation is another debate entirely and not at all the point I was making, sorry if it was unclear
-
The argument is practical Write Haskell; never use orphan instances. This is achievable with little/no penalty Write Scala; never use orphan instances. With this commitment, it's difficult & there's no sweet spot Scala does not have type-classes in any general practical sense
- Show replies
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.