unexceptionalio VS safe-exceptions

Compare unexceptionalio vs safe-exceptions and see what are their differences.

Our great sponsors
  • WorkOS - The modern identity platform for B2B SaaS
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • SaaSHub - Software Alternatives and Reviews
unexceptionalio safe-exceptions
- 3
28 132
- 0.0%
0.0 3.4
almost 4 years ago 6 months ago
Haskell Haskell
LicenseRef-OtherLicense MIT License
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.

unexceptionalio

Posts with mentions or reviews of unexceptionalio. We have used some of these posts to build our list of alternatives and similar projects.

We haven't tracked posts mentioning unexceptionalio yet.
Tracking mentions began in Dec 2020.

safe-exceptions

Posts with mentions or reviews of safe-exceptions. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2021-03-21.
  • Spooky Masks and Async Exceptions
    1 project | /r/haskell | 30 Oct 2022
    In case anyone is interested, there's a long discussion on this ticket. Still hoping somebody will respond to my comment.
  • Async Control Flow
    7 projects | /r/haskell | 21 Mar 2021
    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
    6 projects | /r/haskell | 9 Jan 2021
    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.

What are some alternatives?

When comparing unexceptionalio and safe-exceptions you can also consider the following projects:

monad-validate - (NOTE: REPOSITORY MOVED TO NEW OWNER: https://github.com/lexi-lambda/monad-validate) A Haskell monad transformer library for data validation

ifcxt - constraint level if statements

these - An either-or-both data type, with corresponding hybrid error/writer monad transformer.

atl - Arrow Transformer Library

fused-effects - A fast, flexible, fused effect system for Haskell

effect-monad - Provides 'graded monads' and 'parameterised monads' to Haskell, enabling fine-grained reasoning about effects.

throwable-exceptions - Give the exception's value constructors for your haskell project

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)

foldl - Composable, streaming, and efficient left folds

recursion-schemes - Generalized bananas, lenses and barbed wire

tardis

time-warp