Skip to content
Commits on Sep 12, 2013
  1. @timo

    chase rakudo CALLER:: semantics.

    timo committed
Commits on Jul 27, 2013
  1. @timo
  2. @timo
Commits on Apr 2, 2009
  1. wrote twenty-ninth test

    committed
  2. wrote 28th test; passes right away

    committed
    However, I can make it fail by removing a line from last commit, so it's fine.
  3. wrote tests 26 and 27; 26 fails

    committed
  4. added, wrote twenty-fifth test

    committed
Commits on Mar 31, 2009
  1. wrote twenty-second test

    committed
  2. made twenty-first test pass

    committed
  3. wrote twenty-first test

    committed
  4. wrote nineteenth test

    committed
  5. wrote eighteenth test

    committed
    It passes, even though it shouldn't.
  6. rethought swapping mechanics

    committed
    jonalv++
  7. replaced ~~ Failure with !defined

    committed
    Looks nicer. Theoretically, I could just test for boolean truth, but that
    feels a bit too implicit.
Commits on Mar 23, 2009
  1. added sixteenth test

    committed
    Also corrected a few previous tests that checked for death instead of failure.
    This made the fifth test die.
  2. implemented fourteenth test

    committed
    This uncovered a bug in Druid::Game which made it die
  3. corrected tests ten and eleven

    committed
    They turned out not to have been converted to the new semantics of failure
    instead of death, and only passed before because of the lack of casting in
    Druid::Game. Who watches the watchers?
Commits on Mar 22, 2009
  1. fixed syntax of two tests

    committed
    The implementation changed under them. Illegal moves now fail instead of
    dying.
Commits on Mar 21, 2009
  1. implemented eleventh test

    committed
  2. wrote ninth test -- passes right away

    committed
    Also rewrote a previous test to test only one thing.
Commits on Mar 20, 2009
  1. implemented eighth test; it fails

    committed
Commits on Mar 19, 2009
  1. [Druid::Game] s/make_move/make-move/

    committed
    Also ditched the redundant color parameter.
Something went wrong with that request. Please try again.