2 ms·
It's not worth responding to people like that, but it's funny now to point out that Wadler says in the Featherweight Go video that Go's type system has somethin
by chubot 6y ago
It's not worth responding to people like that, but it's funny now to point out that Wadler says in the Featherweight Go video that Go's type system has something that Haskell's type system may like to borrow, i.e. that interface types are open:
https://www.youtube.com/watch?v=Dq0WFigax_c https://www.youtube.com/watch?v=Dq0WFigax_c
It's somewhere in the first 10-20 minutes (if someone wants to give a timestamp link)
(Also, my experience is that such comments usually get downvoted/flagged on HN, you just have to wait awhile)
- tosh 6y agohttps://youtu.be/Dq0WFigax_c?t=912 https://youtu.be/Dq0WFigax_c?t=912 (on closed vs open and haskell)
- tome 6y agoI'm not sure what Philip meant there, but I don't see this as a particularly notable weakness of Haskell's type class system. We can already encode an open world through the standard "HasX"-style classes. There's a good reason that we don't use them much, though: type classes are typically not just interfaces but come with laws expressing how they should behave. It's not clear to me how those laws interact with an open world.