hpc-coveralls VS safe-exceptions

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

hpc-coveralls

coveralls.io support for haskell code coverage with hpc (by killy971)

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
hpc-coveralls safe-exceptions
0 3
60 132
- 0.0%
4.3 3.4
7 months ago 5 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.

hpc-coveralls

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

We haven't tracked posts mentioning hpc-coveralls 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.
  • 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 hpc-coveralls and safe-exceptions you can also consider the following projects:

capability - Extensional capabilities and deriving combinators

frpnow

unexceptionalio - IO without any PseudoExceptions

ifcxt - constraint level if statements

atl - Arrow Transformer Library

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

ConstraintKinds - Implements common Haskell type classes using the constraint kinds pattern to allow constraints.

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)

recursion-schemes - Generalized bananas, lenses and barbed wire

apecs - a fast, extensible, type driven Haskell ECS framework for games

time-warp

rio-orphans - A standard library for Haskell