@bitemyapp monads are usually used *in place of* constructs that are non-local and create annoying global protocols.
-
-
Replying to @wycats
@wycats What is non-local about this? This is very common.pic.twitter.com/y0H1QDwQ6V
2 replies 0 retweets 0 likes -
Replying to @bitemyapp
@bitemyapp what would this look like in a non-monadic style?1 reply 0 retweets 0 likes -
-
Replying to @bitemyapp
@bitemyapp and what is the benefit of writing that code in a monadic style as opposed to the non-monadic style?1 reply 0 retweets 0 likes -
Replying to @bitemyapp
@wycats but I can only abstract this out because I have higher kinded types, typeclasses, etc.1 reply 0 retweets 0 likes -
Replying to @bitemyapp
@wycats also, all these functions: http://hackage.haskell.org/package/base-4.8.1.0/docs/Control-Monad.html …1 reply 0 retweets 0 likes -
Replying to @bitemyapp
@wycats anytime I have a datatype that has a Monad instance and one of those functions matches the type I want, I can use it.1 reply 0 retweets 0 likes -
Replying to @bitemyapp
@wycats This is not hypothetical. I write Haskell 9-5 and work on http://haskellbook.com/ in my free time. This stuff is my daily bread.3 replies 0 retweets 0 likes
@bitemyapp I don't doubt your credentials, and haven't challenged them. The same cannot be said in reverse.
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.