This is great. The only problem (as with Eff) is composing certain effects lawfully (print and read have no laws).
-
-
What would that mean though? What laws could otherwise come about to give a benefit? The classy prism is as lawful as it gets.
1 reply 0 retweets 0 likes -
If your algebra had throwError and catchError (as MonadError), then that has laws, which can't mix symmetrically with MonadCont.
1 reply 0 retweets 0 likes -
Why do I even want these things?
1 reply 0 retweets 0 likes -
I find MonadError's effects just part of life; the world of MonadCont's utility is still a world I need to explore more (
@kmett?).2 replies 0 retweets 0 likes -
Replying to @shajra @etorreborre and
I don't think it applies to this case. It seems unnecessary.
1 reply 0 retweets 1 like -
Replying to @dibblego @etorreborre and
If your effects indeed compose the way you want, then by all means Eff or Free away.
2 replies 0 retweets 0 likes -
Replying to @shajra @etorreborre and
I use MonadError (misnamed MonadEither) in the error case. This just isn't that case.
2 replies 0 retweets 0 likes -
Replying to @dibblego @etorreborre and
Actually, I agree with this. But I don't know how many other gotchas there are beyond Cont/Error.
1 reply 0 retweets 0 likes -
I like how
@kmett caught me off guard when I asked him what he thought about "extensible effects," and he replied "they don't exist."1 reply 0 retweets 3 likes
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.