Came up in a discussion with @bitonic. There's no downside I can see to the MonadCatch instance. However, the MonadMask instance is a little bit more controversial, in that it's not actually doing any masking. However, it's impossible to know that it's not masking the async exceptions since there are no side-effects from the Either monad. Of course, by using unsafePerformIO, we could observe the difference, but I think that's a valid trade-off. One final argument against MonadMask for Either: it's probably not terribly useful.
| Name | Last commit | Last update |
|---|---|---|
| src/Control/Monad | ||
| tests | ||
| travis | ||
| .ghci | ||
| .gitignore | ||
| .travis.yml | ||
| .vim.custom | ||
| AUTHORS.markdown | ||
| CHANGELOG.markdown | ||
| LICENSE | ||
| README.markdown | ||
| Setup.lhs | ||
| exceptions.cabal |
This package provides (optionally pure) extensible exceptions that are compatible with the monad transformer library.
Contributions and bug reports are welcome!
Please feel free to contact me through github or on the #haskell IRC channel on irc.freenode.net.
-Edward Kmett