Initiatives:

Tier 1:
- Performance - most likely need CPS optimization and closure elimination
- pass larceny benchmarks (will require some bugfixes):
  TODO: keep track of which ones will not run, and why

    - ack.scm
    - array1.scm
    - browse.scm
    - bv2string.scm
    - cat.scm - Fails, unable to open outputs/cat.output. Seems opening a file in a directory that does not exist is failing. Is that behavior specified?
    - compiler.scm - Error: Unhandled number of function arguments: 1348
    - conform.scm
    - cpstak.scm
    - ctak.scm
    - deriv.scm
    - destruc.scm
    - diviter.scm
    - divrec.scm
    - dynamic.scm - Unhandled number of function arguments: 234
    - earley.scm
    - equal.scm
    - fft.scm
    - fibc.scm
    - fibfp.scm
    - fib.scm
    - gcbench.scm - Needed to manually import (srfi 9)
    - graphs.scm
    - lattice.scm - Error: run: unanticipated problem size 44. may be a problem with numbers and (case)
    - matrix.scm
    - mazefun.scm
    - maze.scm - There is a problem reading the input file
    - mbrot.scm
    - mbrotZ.scm - No complex library
    - mperm.scm
    - nboyer.scm
    - nqueens.scm
    - ntakl.scm
    - nucleic.scm - Unhandled number of function arguments: 266
    - paraffins.scm
    - parsing.scm
    - peval.scm
    - pi.scm
    - pnpoly.scm
    - primes.scm
    - puzzle.scm
    - quicksort.scm
    - ray.scm -  Error: Unable to open file outputs/ray.output. similar issue to above?
    - read0.scm - Error (line 170, char 25): unable to parse character: x3bb
    - read1.scm
    - sboyer.scm
    - scheme.scm - Problem with (macro?) being a primitive and defined in application code
    - simplex.scm - Compiles but quickly throws error Error: Divide by zero
    - slatex.scm - Unhandled number of function arguments: 188
    - string.scm
    - sum1.scm
    - sumfp.scm
    - sum.scm
    - tail.scm - Unable to open file outputs/tail.output
    - takl.scm
    - tak.scm
    - triangl.scm
    - wc.scm


Tier 2:
- srfi 18 - more complex threading examples (probably can wait)
- api documentation (can wait?)
- online docs via read-the-docs?
- higher priority issues (need to be resolved, but can wait?)
  - revisit macro hygiene issues
  - library issues (name conflicts and limited feature set)