exitcode
exceptions
| exitcode | exceptions | |
|---|---|---|
| - | 1 | |
| 1 | 48 | |
| - | - | |
| 4.8 | 5.4 | |
| 7 months ago | 10 days ago | |
| Haskell | Haskell | |
| BSD 3-clause "New" or "Revised" License | BSD 3-clause "New" or "Revised" License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
exitcode
We haven't tracked posts mentioning exitcode yet.
Tracking mentions began in Dec 2020.
exceptions
-
Async Control Flow
I see. Do you think rethrowing the original exception is the the right approach in all cases, or only in this case? In the documentation I wrote for the exceptions package, I recommend to let the release block's exceptions take priority, to match base's behavior. Should I recommend the opposite?
What are some alternatives?
ImperativeHaskell - Proof that Haskell can look and act like an imperative language.
either - the EitherT monad transformer
monad-logger-prefix - Easily add a prefix to your MonadLogger output.
control-monad-exception - Explicitly Typed exceptions as a library
apecs - a fast, extensible, type driven Haskell ECS framework for games
failure - A simple type class for success/failure computations.
pipes-parse - Parsing for the pipes ecosystem
categories - categories from category-extras
retry - Retry combinators for monadic actions that may fail
control-monad-omega - A Haskell monad for fair enumeration of infinite sets.
freer-effects - An implementation of "Freer Monads, More Extensible Effects".
hask - Category theory for Haskell with a lens flavor (you need GHC 7.8.3, not 7.8.2 to build this!)