@djspiewak @nuttycom @jdegoes @milessabin Tell me what haskell gets wrong in this regard. Do not fail.
-
-
Replying to @dibblego
@dibblego@nuttycom@jdegoes@milessabin I’ve already listed a trivial example which proves the distinction is arbitrary.1 reply 0 retweets 0 likes -
Replying to @djspiewak
@djspiewak@nuttycom@jdegoes@milessabin No, you really haven't. And worse, not even close.1 reply 0 retweets 0 likes -
Replying to @dibblego
@dibblego@nuttycom@jdegoes@milessabin Yes, I really have. Do you want me to instead show a type that has more than one valid Monad?1 reply 0 retweets 0 likes -
Replying to @djspiewak
@djspiewak@nuttycom@jdegoes@milessabin Yes, because I can't think of one and that will totally demonstrate your point!6 replies 0 retweets 0 likes -
Replying to @dibblego
@dibblego@nuttycom@jdegoes@milessabin An utterly useless example of a type with two (both valid!) monads: http://pastebin.com/C6WX8kkP1 reply 0 retweets 0 likes -
Replying to @djspiewak
@djspiewak@nuttycom@jdegoes@milessabin Yes thanks. Note demonstrate the connection to your conclusion. No failing.3 replies 0 retweets 0 likes -
Replying to @dibblego
@dibblego@nuttycom@jdegoes@milessabin My conclusion is far less broad than you think it is.1 reply 0 retweets 0 likes -
Replying to @djspiewak
@djspiewak@nuttycom@jdegoes@milessabin if it is anything but multiple instances per type is outrageous, then no.1 reply 0 retweets 0 likes -
Replying to @dibblego
@dibblego@nuttycom@jdegoes@milessabin My conclusion is that having an *enforced* single instance per type is arbitrary.2 replies 0 retweets 0 likes
@djspiewak @nuttycom @jdegoes @milessabin You do realise that I could give instances for every type ad infinitum right?
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.