4d289d4488
From my experience, while topics usually cover different methodologies of working with exceptions, real programs and libs in non-small apps use them all, so you have to combine or make sure you can convert between all possible types easily.
1.1 KiB
1.1 KiB
| title | author | description | first-written | last-updated | last-reviewed |
|---|---|---|---|---|---|
| All About Exceptions | Michael Snoyman <michael@fpcomplete.com> | All of the necessary information to understand exceptions | 2015-02-24 | 2015-02-24 | 2015-02-24 |
Should cover:
- Throwing exceptions
- Catching exceptions
- Exceptions in pure code
- Difference between
throwandthrowIO - Async exceptions
- Catching all exceptions
- http://www.yesodweb.com/blog/2014/05/exceptions-cont-monads
- https://www.fpcomplete.com/user/snoyberg/general-haskell/exceptions/exceptions-and-monad-transformers
- https://www.fpcomplete.com/user/snoyberg/general-haskell/exceptions/catching-all-exceptions
- Exceptions problems. Can't wrap. Can't have two exceptions. No idea how exception was thrown.
- Wrap exceptions to provide context
- General dislike of exceptions
- enclosed-exceptions
- Examples of code-conversion between all possible error styles
- unexceptionalio and errors libraries