Ben Foppa wrote:
Uploader and current maintainer of the extensible-effects package here. Although I'm still confused myself about the more theoretical bits of extensible-effects, I think I might be able to shed some light on it from a user's and maintainer's perspective.
extensible-effects is currently operational, and works quite well wherever I use it. That said, it's a new package and I'd expect some shifts before it settles down.
Let me first say that I like the general idea very much. I just read the paper and it all looks extremely promising. And I greatly appreciate your effort to put it on hackage and maintain it. It is a good thing that the library is not yet settled, though, because I think some of the names should be re-considered. For instance, why Eff and not Effect? Or why type Exn but corresponding functions throwError and catchError? (IMO such slips are okay for a paper, or a proof-of-concept implementation, but not for a library that aspires to overthrow monad transformers.) Cheers Ben -- "Make it so they have to reboot after every typo." -- Scott Adams