Conditionally labels test case.

indentation of a class or instance

Focuses on using common typeclasses when possible, and creating new ones to avoid name clashing. Exposes many recommended datastructures (Map, ByteString, etc) directly without requiring long import lists and qualified modules.
Version 0.7.0

conduit instances for classy-prelude
Version 0.7.0

This is an extension of classy-prelude-conduit, adding in commonly used functions and data types from Yesod.
Version 0.7.0

* *Computation type:* Computations which can be interrupted and resumed.
* *Binding strategy:* Binding a function to a monadic value creates a new continuation which uses the function as the continuation of the monadic computation.
* *Useful for:* Complex control structures, error handling, and creating co-routines.
* *Zero and plus:* None.
* *Example type:* Cont r a
The Continuation monad represents computations in continuation-passing style (CPS). In continuation-passing style function result is not returned, but instead is passed to another function, received as a parameter (continuation). Computations are built up from sequences of nested continuations, terminated by a final continuation (often id) which produces the final result. Since continuations are functions which represent the future of a computation, manipulation of the continuation functions can achieve complex manipulations of the future of the computation, such as interrupting a computation in the middle, aborting a portion of a computation, restarting a computation, and interleaving execution of computations. The Continuation monad adapts CPS to the structure of a monad.
Before using the Continuation monad, be sure that you have a firm understanding of continuation-passing style and that continuations represent the best solution to your particular design problem. Many algorithms which require continuations in other languages do not require them in Haskell, due to Haskell's lazy semantics. Abuse of the Continuation monad can produce code that is impossible to understand and maintain.

* *Computation type:* Computations which may fail or throw exceptions.
* *Binding strategy:* Failure records information about the cause/location of the failure. Failure values bypass the bound function, other values are used as inputs to the bound function.
* *Useful for:* Building computations from sequences of functions that may fail or using exception handling to structure error handling.
* *Zero and plus:* Zero is represented by an empty error and the plus operation executes its second argument if the first fails.
* *Example type:* Either String a
The Error monad (also called the Exception monad).

Class of monads based on IO.

* *Computation type:* Computations which read values from a shared environment.
* *Binding strategy:* Monad values are functions from the environment to a value. The bound function is applied to the bound value, and both have access to the shared environment.
* *Useful for:* Maintaining variable bindings, or other shared environment.
* *Zero and plus:* None.
* *Example type:* Reader [(String,Value)] a
The Reader monad (also called the Environment monad). Represents a computation, which can read values from a shared environment, pass values from function to function, and execute sub-computations in a modified environment. Using Reader monad for such computations is often clearer and easier than using the State monad.
Inspired by the paper *Functional Programming with Overloading and Higher-Order Polymorphism*, Mark P Jones (http://web.cecs.pdx.edu/~mpj/) Advanced School of Functional Programming, 1995.

Declaration of the MonadRWS class.
Inspired by the paper *Functional Programming with Overloading and Higher-Order Polymorphism*, Mark P Jones (http://web.cecs.pdx.edu/~mpj/) Advanced School of Functional Programming, 1995.

MonadState class.
This module is inspired by the paper *Functional Programming with Overloading and Higher-Order Polymorphism*, Mark P Jones (http://web.cecs.pdx.edu/~mpj/) Advanced School of Functional Programming, 1995.

Classes for monad transformers.
A monad transformer makes a new monad out of an existing monad, such that computations of the old monad may be embedded in the new one. To construct a monad with a desired set of features, one typically starts with a base monad, such as Identity, [] or IO, and applies a sequence of monad transformers.
Most monad transformer modules include the special case of applying the transformer to Identity. For example, State s is an abbreviation for StateT s Identity.
Each monad transformer also comes with an operation run*XXX* to unwrap the transformer, exposing a computation of the inner monad.

The MonadWriter class.
Inspired by the paper *Functional Programming with Overloading and Higher-Order Polymorphism*, Mark P Jones (http://web.cecs.pdx.edu/~mpj/pubs/springschool.html) Advanced School of Functional Programming, 1995.

> { class Eq a => Ord a

A class, with a list of its visible instances

The specification of a class in Haskell often starts with stating, in text, the laws that should be satisfied by methods defined in instances of the class, followed by the type of the methods of the class. The ClassLaws library is a framework that supports testing such class laws using QuickCheck. Our framework is a light-weight class law testing framework, which requires a limited amount of work per class law, and per datatype for which the class law is tested. We also show how to test class laws with partially-defined values. Using partially-defined values, we show that the standard lazy and strict implementations of the state monad do not satisfy the expected laws. More information can be found at http://wiki.portal.chalmers.se/cse/pmwiki.php/FP/ClassLaws. Built with ghc-7.4.2 and ghc-7.6.1. (Fails to build with ghc-7.2.2 due to http://hackage.haskell.org/trac/ghc/ticket/5745. Could be worked around.)
Version 0.3.1.0