neither: Provide versions of Either with good monad and applicative instances. (deprecated)
The standard Either datatype suffers from a lack of monad and applicative instances. To make matters worse, the mtl and transformers packages provide orphan instances which conflict with each other, as well as defining a transformer version which has an usually unnecessary superclass constraint.
Besides these annoyances, there is another issue: there exist two reasonable definitions of the Applicative instance for Either: one the holds onto only the first Left value, or one that appends all Left values together via a Monoid instance. The former is compatible with the monad instance, while the latter is not.
This package defines three datatypes, some helpers functions and instances. The data types are AEither, MEither and MEitherT. AEither provides an Applicative instance which appends Left values, MEither provides the monadic definition, and MEitherT is a monad transformer.
|Versions [faq]||0.0.0, 0.0.1, 0.0.2, 0.1.0, 0.2.0, 0.3.0, 0.3.0.1, 0.3.1, 0.3.1.1|
|Dependencies||base (==4.*), failure (>=0.1.0 && <0.3), transformers (>=0.2.1 && <0.4) [details]|
|Author||Michael Snoyman <email@example.com>|
|Maintainer||Michael Snoyman <firstname.lastname@example.org>|
|Source repo||head: git clone git://github.com/snoyberg/neither.git|
|Uploaded||by MichaelSnoyman at 2012-05-14T03:01:19Z|
|Downloads||5718 total (2 in the last 30 days)|
|Rating||(no votes yet) [estimated by Bayesian average]|
Docs uploaded by user
Build status unknown [no reports yet]
For package maintainers and hackage trustees