Death to type classes
jappie.me
Death to type classes
1–10 of 78 posts
Re: Death to type classes
#2Re: Death to type classes
#3Re: Death to type classes
#4I feel like this article would be much more approachable if it didn't assume readers already know Ocaml and Haskell and their module system
(I have a t-shirt with a lambda in a circle, reminiscent of the anarchist emblem, and words "no class, no state". It's definitely possible to explain to a passer-by who never studied FP what it refers to, but not in such a way that the joke remained funny. Possibly the same deal is with the bumper sticker saying "my other car is cdr".)
Re: Death to type classes
#5I feel like this article would be much more approachable if it didn't assume readers already know Ocaml and Haskell and their module system
Re: Death to type classes
#6I feel like this article would be much more approachable if it didn't assume readers already know Ocaml and Haskell and their module system
Re: Death to type classes
#7I feel like this article would be much more approachable if it didn't assume readers already know Ocaml and Haskell and their module system
Indeed so, but that would require a few months worth of work from the reader, unfortunately. (I have a t-shirt with a lambda in a circle, reminiscent of the anarchist emblem, and words "no class, no state". It's definitely possible to explain to a passer-by who never studied FP what it refers to, but not in such a way that the joke remained funny. Possibly the same deal is with the bumper sticker saying "my other car…
Re: Death to type classes
#8I feel like this article would be much more approachable if it didn't assume readers already know Ocaml and Haskell and their module system
Re: Death to type classes
#9Re: Death to type classes
#10 if err !== nil {
return err
}