control-monad-omega
exceptions
control-monad-omega | exceptions | |
---|---|---|
- | 1 | |
10 | 48 | |
- | - | |
0.0 | 5.4 | |
over 4 years ago | 10 days ago | |
Haskell | Haskell | |
LicenseRef-PublicDomain | 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.
control-monad-omega
We haven't tracked posts mentioning control-monad-omega 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?
operational - Implement monads by specifying instructions and their desired operational semantics.
either - the EitherT monad transformer
control-monad-exception - Explicitly Typed exceptions as a library
failure - A simple type class for success/failure computations.
categories - categories from category-extras
hask - Category theory for Haskell with a lens flavor (you need GHC 7.8.3, not 7.8.2 to build this!)
cloud-haskell - This is an umbrella development repository for Cloud Haskell
funflow - Functional workflows
apart - Get all your structure and rip it apart.
apecs - a fast, extensible, type driven Haskell ECS framework for games
errors - Type-safe error handling
lifted-base - IO operations from the base library lifted to any instance of MonadBase or MonadBaseControl