ifcxt VS safe-exceptions

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

ifcxt

constraint level if statements (by mikeizbicki)

safe-exceptions

Safe, consistent, and easy exception handling (by fpco)
Our great sponsors
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • WorkOS - The modern identity platform for B2B SaaS
  • SaaSHub - Software Alternatives and Reviews
ifcxt safe-exceptions
4 3
110 132
- 0.0%
0.0 3.4
over 6 years ago 6 months ago
Haskell Haskell
BSD 3-clause "New" or "Revised" License 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.

ifcxt

Posts with mentions or reviews of ifcxt. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2022-08-02.

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 ifcxt and safe-exceptions you can also consider the following projects:

capability - Extensional capabilities and deriving combinators

unexceptionalio - IO without any PseudoExceptions

auto - Haskell DSL and platform providing denotational, compositional api for discrete-step, locally stateful, interactive programs, games & automations. http://hackage.haskell.org/package/auto

atl - Arrow Transformer Library

transient-universe - A Cloud monad based on transient for the creation of Web and reactive distributed applications that are fully composable, where Web browsers are first class nodes in the cloud

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

rio-orphans - A standard library for Haskell

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)

objective - Purely functional objects

time-warp

recursion-schemes - Generalized bananas, lenses and barbed wire