Timeline for What is the difference between Haskell's type classes and Go's interfaces?
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 21, 2016 at 8:09 | comment | added | ceving | Can you explain the example in 3? What does it mean? | |
| Dec 20, 2016 at 15:36 | comment | added | ceving | @walpen Why does this break code? I wonder how such code could exist considering the strictness of Haskell's type system. | |
| Dec 20, 2016 at 15:08 | comment | added | walpen | @JörgWMittag I'll agree there and I liked your answer: I was trying to get at more of the difference from the users perspective. | |
| Dec 20, 2016 at 15:07 | comment | added | walpen | @ceving, it's definitely not sugar in the normal sense: if Haskell jumped to something like Scala implicits for type classes it would break a lot of existing code. | |
| Dec 20, 2016 at 14:55 | comment | added | Jörg W Mittag | Go interfaces define a protocol for values, Haskell type classes define a protocol for types, that is also a pretty major difference, I would say. (That's why they are called "type classes", after all. They classify types, unlike OO classes (or Go's interfaces), which classify values.) | |
| Dec 20, 2016 at 14:41 | comment | added | ceving | Is 1. really a difference or is it just missing sugar? | |
| Dec 20, 2016 at 14:29 | history | answered | walpen | CC BY-SA 3.0 |