Hackage :: [Package]

async-io-either: Could be useful

[ bsd3, error-handling, library ] [ Propose Tags ] [ Report a vulnerability ]

A way of running any IO type and capturing any exception, maybe, I think...

[Skip to Readme]

Modules

[Index]

Downloads

Maintainer's Corner

Package maintainers

For package maintainers and hackage trustees

Candidates

  • No Candidates
Versions [RSS] 0.1.0.0, 0.1.0.1, 0.1.0.2, 0.1.0.3, 0.1.0.4
Dependencies async (>0.2), base (>=4.7 && <5), retry, transformers [details]
License BSD-3-Clause
Copyright 2017 Sean Chalmers
Author Sean Chalmers
Maintainer sclhiannan@gmail.com
Category Error Handling
Home page https://github.com/mankyKitty/async-io-either#readme
Source repo head: git clone https://github.com/mankyKitty/async-io-either
Uploaded by schalmers at 2017-02-21T02:00:47Z
Distributions NixOS:0.1.0.4
Reverse Dependencies 1 direct, 1 indirect [details]
Downloads 3888 total (4 in the last 30 days)
Rating 2.0 (votes: 1) [estimated by Bayesian average]
Your Rating
  • λ
  • λ
  • λ
Status Docs available [build log]
Last success reported on 2017-02-21 [all 1 reports]

Readme for async-io-either-0.1.0.4

[back to package description]

Async IO Either

This is a tiny package that captures a pattern I've been using a lot...

Essentially I am tired of needing something of (IO a) and it so often coming with exceptions that are not indicated in the type. Generally speaking my application, like many others, is just going to throw in the towel when an exception occurs, but I would prefer it if a value was provided. This would then allow me to decide just what sort of tantrum my application will throw.

I've tried to understand the different manners of handling exceptions in Haskell, and I'm sure there is a better or more fitting approach. But this is what I have for now.