plucky: A library and technique for handling errors via plucking constraints

[ bsd3, data, library ] [ Propose Tags ] [ Report a vulnerability ]

Please see the README on GitHub at https://github.com/parsonsmatt/plucky#readme


[Skip to Readme]

Modules

[Index] [Quick Jump]

Downloads

Maintainer's Corner

Package maintainers

For package maintainers and hackage trustees

Candidates

  • No Candidates
Versions [RSS] 0.0.0.0, 0.0.0.1 (info)
Change log ChangeLog.md
Dependencies base (>=4.9.1.0 && <5), transformers (>=0.4.0.0 && <0.6) [details]
License BSD-3-Clause
Copyright 2020 Matt Parsons
Author Matt Parsons
Maintainer parsonsmatt@gmail.com
Category Data
Home page https://github.com/parsonsmatt/plucky#readme
Bug tracker https://github.com/parsonsmatt/plucky/issues
Source repo head: git clone https://github.com/parsonsmatt/plucky
Uploaded by parsonsmatt at 2020-01-21T18:53:40Z
Distributions
Downloads 683 total (5 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 2020-01-21 [all 1 reports]

Readme for plucky-0.0.0.1

[back to package description]

plucky

Build Status

Haskell has a problem with problems. We have IO exceptions for unchecked exceptions - the same sort that plague Ruby, Python, JavaScript, and other languages. We have ExceptT for checked exceptions, but Java has us beat on ergonomics and usability of checked exceptions. Can we do better? Well, the blog post points to generic-lens, but that's kind of hard to use. Can we do better, and easier?

Yes! I alluded to this in my blog post Plucking Constraints. This library provides an API and demonstration on 'plucking' error constraints.