This 10-year old post by just reminded me that it's 2019 and Haskell fan(bois|gyrls) are still dying on the HASKELL TYPE CLASSES ARE THE HOLY WAY hill. So sad.
Conversation
This Tweet was deleted by the Tweet author. Learn more
I like Purescript's named instances
1
Sorry, I think it's Idris that does this.
1
Bottom line: I don't know what the best thing is yet. But Haskell is quite painful in many ways, so I choose to believe that there is some better option out there waiting to be found. :)
I haven't heard any arguments against named instances, but would love to hear some.
2
4
By named instances do you mean non-coherent instances? Ed Kmett did a loong talk "Type Classes vs. The World" which outlined some of the problems. I don't necessarily agree - I'm interested in exploring the modular type classes approach, but it brings up important points.
You definitely want to avoid Scala's situation where you never are sure what instance you have in scope at any time - and the instance resolution algorithm is mysterious and confusing.
1
1
Coherent instances also tend to end up with people relying on it when designing their APIs, so you need to figure out how to train people out relying on that and provide alternatives.
1
Show replies