Commits on May 12, 2010
  1. failure 0.1.0

    committed May 12, 2010
Commits on Apr 25, 2010
Commits on Apr 10, 2010
Commits on Jan 13, 2010
  1. attemptTIO built on attemptIO

    committed Jan 13, 2010
Commits on Jan 12, 2010
Commits on Dec 6, 2009
  1. Minor bookkeeping

    committed Dec 6, 2009
Commits on Dec 5, 2009
Commits on Nov 16, 2009
  1. Fixed Example.lhs

    committed Nov 16, 2009
Commits on Nov 15, 2009
Commits on Nov 14, 2009
Commits on Nov 13, 2009
  1. Call toException at some places

    I think it is safer to use toException even if
    toException discard some information about the
    exception (locations).
    np committed Nov 13, 2009
  2. Reworked the last changes for better extensible support.

    failure calls SomeException, not toException. Otherwise, failure is
    implicitly changing the exception that users throw.
    Removed the extra cast operation in makeHandler. The test passes without
    it, and I don't know why it's necesary. If I see an example that
    requires it, I'll be happy to put it back in.
    committed Nov 13, 2009
Commits on Nov 12, 2009
  1. Fixed the attempt and makeHandler functions.

    Added a test case which showed the need to adjust these functions.
    The test passes now, but I'm not convinced this is the final answer.
    committed Nov 12, 2009
Commits on Nov 10, 2009
Commits on Nov 9, 2009
Commits on Nov 8, 2009
  1. Failure constructor now contains a SomeException.

    This necesitated inserting the stack trace directly in the Failure
    constructor as well. The purpose is to honor the exception hierarchy.
    committed Nov 8, 2009
Commits on Nov 6, 2009
Commits on Oct 26, 2009
  1. Function ideas from Nicolas

    committed Oct 26, 2009
Commits on Oct 25, 2009
Commits on Oct 22, 2009
  1. Added example

    committed Oct 22, 2009
  2. Added fa, assert, readFile

    committed Oct 22, 2009
Commits on Oct 21, 2009
  1. Updated documentation

    committed Oct 21, 2009
  2. Functor superclass; evalAttemptT; removed success.

    Success should always be just a synonym for return, so why have it?
    It was getting annoying not being able to call fmap where ever I wanted.
    I'd like to make Applicative a superclass too, but we know some people
    don't define their Monads properly.
    evalAttemptT is something I've wanted, it just took a while to come up
    with a name. Thought about drop, since it's really the opposite of lift.
    committed Oct 21, 2009