async-io-either: Could be useful

[ bsd3, error-handling, library ] [ Propose Tags ]

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

[Skip to Readme]

Modules

[Index]

Control
- Concurrent
  - Async
    - Control.Concurrent.Async.Either

Downloads

async-io-either-0.1.0.2.tar.gz [browse] (Cabal source package)
Package description (as included in the package)

Maintainer's Corner

Package maintainers

schalmers

For package maintainers and hackage trustees

edit package information

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), 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-20T06:08:15Z
Distributions	NixOS:0.1.0.4
Reverse Dependencies	1 direct, 1 indirect [details]
Downloads	3871 total (23 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-20 [all 1 reports]

Readme for async-io-either-0.1.0.2

[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.