homepage: https://github.com/parsonsmatt/plucky#readme
changelog-type: markdown
hash: ba0882bb5efd5f90a90fe0bd90d6b27bad0c56e8317ab64335e2c1f342456560
test-bench-deps:
  base: ! '>=4.7 && <5'
  mtl: -any
  plucky: -any
maintainer: parsonsmatt@gmail.com
synopsis: A library and technique for handling errors via plucking constraints
changelog: |
  # Changelog for checked-errors

  ## Unreleased changes
basic-deps:
  base: ! '>=4.9.1.0 && <5'
  transformers: ! '>=0.4.0.0 && <0.6'
all-versions:
- 0.0.0.0
author: Matt Parsons
latest: 0.0.0.0
description-type: markdown
description: |
  # plucky

  [![Build Status](https://travis-ci.org/parsonsmatt/plucky.svg?branch=master)](https://travis-ci.org/parsonsmatt/plucky)

  Haskell [has a problem with problems](https://www.parsonsmatt.org/2018/11/03/trouble_with_typed_errors.html).
  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`](https://hackage.haskell.org/package/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](https://www.parsonsmatt.org/2020/01/03/plucking_constraints.html).
  This library provides an API and demonstration on 'plucking' error constraints.
license-name: BSD-3-Clause

Update from Hackage at 2020-01-21T17:47:34Z
Update from Hackage at 2020-01-21T17:47:34Z
