repeatedly-into as a macro
move thaw exception handler outside of `thaw` (it's recreated everytime the function gets called now)
Housekeeping
Make `coll-thaw`, `coll-thaw-kvs` macros (performance)
Reorganize low-level stream fns (prepping for perf work)
Rewrite all stream helpers as macros (performance)
Update benchmarks (2.0.0-alpha6)
Bump version (2.0.0-alpha6)
Merge branch 'dev'
Clean up benchmarks chart
Auto AES128 block size
Rename default compressor, encryptor
Fix core dump issue (important), simplify API

PROBLEM: :legacy-mode :auto/true thawing was resulting in JVM core
dumps when attempting to use Snappy to decompress encrypted data.

CAUSE: The org.iq80.snappy implementation seems to choke on the
random IV byte data being generated by the AES128 encrypter. This
may or may not be a bug (still awaiting feedback from lib's authors).

SOLUTION: We're only susceptible to this issue when trying to
decompress data that is: a) encrypted, b) being thawed in legacy mode.
In particular, we're _not_ susceptible to this issue when thawing
in non-legacy mode because in that case we have a header explicitly
warning us that the data is encrypted.

An obvious work-around, therefore, is just to disable decryption when
attempting to thaw legacy-mode data. In practice this isn't a problem
because older versions of Nippy didn't support encryption anyway.
Merge branch 'dev'
try non sync version of byte-array iostreams
Merge pull request #10 from mpenet/fast-streams

non sync version of byte-array iostreams (from Apache Harmony, also used in Cassandra)
Housekeeping for 67633d5
Update benchmarks (2.0.0-alpha6 w/fast io-streams)
Bump version (2.0.0-alpha8)
Merge branch 'dev'