Commit 7e5bd61 merges an expanded performance-test branch to master, but this still needs work.
- It's obvious that I don't know my way around Caliper, so I imagine potential improvements would become apparent by investing some time in learning that better.
- Ideally, I'd like the benchmark results to provide results as characters/second, but I have no idea how I might go about doing that with caliper.
- currently, benchmark times include the overhead of opening and closing the reader as well as the associated IO of the underlying characters. That has advantages, since it exercises the more complex of the two Parseable implementations. OTOH, parsing directly out of a String already in memory would produce less variable results.
- I've not added performance tests for Printing. Printing itself is still in an early implementation, but it would be good to get something in place for detecting performance changes there too.
Commit 7e5bd61 merges an expanded performance-test branch to master, but this still needs work.