* TODO Refactoring [1/4]
- [X] Fix up logging
- [ ] Separate classes into files
- [ ] Put outer-loop in a class (out of main)
- [ ] Give EquationSystem methods for creating assignments/strategies

* TODO Verbosity [2/3]
- [X] Wrap output streams [5/5]
  - [X] strategies
  - [X] fixpoint
  - [X] debug
  - [X] trace
  - [X] info
- [X] Command-line arguments [5/5]
  - [X] strategies
  - [X] fixpoint
  - [X] debug
  - [X] trace
  - [X] info
- [-] Provide output [0/5]
  - [-] strategies [1/2]
    - [ ] print the system and assignment, then the next strategy
    - [X] print each strategy like this:
      max(0, x, sub(y,2)) --[2]-> sub(y,2)
  - [ ] fixpoint
    print the system we're working with, then print the resultant assignment
  - [ ] debug
    print the initial system we're working with
    print more general info in the main loop (number of loops, each assignment/strategy)
  - [ ] trace
    maybe we don't need this
    would be something like "entering/exiting" everything mildly important
  - [ ] info
    print the initial system we're working with
    
* TODO make test [2/4]
- [-] write test cases [1/4]
  - [X] examples from paper
  - [ ] best cases
  - [ ] worst cases
  - [ ] average cases
- [ ] work out correct outputs for each test case
- [X] write a script to run over each test case and return pass/fail
- [X] consolidate into makefile as `make test`

* TODO Parametrise EquationSystem for Variable, too [0/1]
- [ ] Give EquationSystem a template parameter for Variable
  I don't think this is necessary, but Thomas wants it

* TODO Min-cost flow problem [0/3]
- [ ] Research min-cost flow libraries
  Potentially just use LEMON? It looks pretty decent.
- [ ] Implement the min-cost flow operator MCF
- [ ] Update test cases to include MCF

* TODO Presentation [0/2]
- [ ] Simplify "Even Faster" solver for explanation
- [ ] Make slides