safe-exceptions
exceptions
Our great sponsors
| safe-exceptions | exceptions | |
|---|---|---|
| 3 | 1 | |
| 132 | 48 | |
| 0.0% | - | |
| 3.4 | 5.4 | |
| 6 months ago | 3 days ago | |
| Haskell | Haskell | |
| MIT 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.
safe-exceptions
-
Spooky Masks and Async Exceptions
In case anyone is interested, there's a long discussion on this ticket. Still hoping somebody will respond to my comment.
-
Async Control Flow
In safe-exception and uniftio it was decided to rethrow the original exception exactly because they decided to use uninterruptibleMask, see here for details.
-
Why exactly I want Boring Haskell to happen
unliftio (and safe-exceptions) contains a very controversial choice of of using uninterruptibleMask inside its bracket. The argument for it seem to come from this issue and comes from the fact that one of the most popular resource finalizers hClose is interruptible. This is a simplification. It is interruptible only if a file handle is used concurrently. Such usage of file handles is rather odd, and it suggest wrong architecture, for example leaking file handles using concurrency. When using file handles in synchronous setting, what withFile pattern encourages, hClose will not block and thus mask is enough.
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?
ifcxt - constraint level if statements
either - the EitherT monad transformer
unexceptionalio - IO without any PseudoExceptions
control-monad-exception - Explicitly Typed exceptions as a library
atl - Arrow Transformer Library
failure - A simple type class for success/failure computations.
effect-monad - Provides 'graded monads' and 'parameterised monads' to Haskell, enabling fine-grained reasoning about effects.
categories - categories from category-extras
transient - A full stack, reactive architecture for general purpose programming. Algebraic and monadically composable primitives for concurrency, parallelism, event handling, transactions, multithreading, Web, and distributed computing with complete de-inversion of control (No callbacks, no blocking, pure state)
control-monad-omega - A Haskell monad for fair enumeration of infinite sets.
time-warp
hask - Category theory for Haskell with a lens flavor (you need GHC 7.8.3, not 7.8.2 to build this!)