control-monad-exception VS exceptions

Compare control-monad-exception vs exceptions and see what are their differences.

control-monad-exception

Explicitly Typed exceptions as a library (by pepeiborra)
Control
Source Code
pepeiborra.github.com
Suggest alternative
Edit details

exceptions

mtl friendly exceptions (by ekmett)
Control
Source Code
Suggest alternative
Edit details
InfluxDB
Our great sponsors
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • WorkOS - The modern identity platform for B2B SaaS
  • SaaSHub - Software Alternatives and Reviews
Our great sponsors
control-monad-exception exceptions
- 1
22 48
- -
1.8 4.4
over 3 years ago 4 months ago
Haskell Haskell
LicenseRef-PublicDomain BSD 3-clause "New" or "Revised" 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.

control-monad-exception

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

We haven't tracked posts mentioning control-monad-exception yet.
Tracking mentions began in Dec 2020.

exceptions

Posts with mentions or reviews of 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
    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?

When comparing control-monad-exception and exceptions you can also consider the following projects:

extensible-effects - Extensible Effects: An Alternative to Monad Transformers

either - the EitherT monad transformer

monad-control - Lift control operations, like exception catching, through monad transformers

failure - A simple type class for success/failure computations.

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

control-monad-omega - A Haskell monad for fair enumeration of infinite sets.

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

categories - categories from category-extras

capability - Extensional capabilities and deriving combinators

hask - Category theory for Haskell with a lens flavor (you need GHC 7.8.3, not 7.8.2 to build this!)

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

cloud-haskell - This is an umbrella development repository for Cloud Haskell

control-monad-exception vs extensible-effects exceptions vs either control-monad-exception vs monad-control exceptions vs failure control-monad-exception vs fused-effects exceptions vs control-monad-omega control-monad-exception vs these exceptions vs categories control-monad-exception vs capability exceptions vs hask control-monad-exception vs effect-monad exceptions vs cloud-haskell