Remove binary.{Read,Write} in favour of doing it by hand

The encoding/binary.{Read,Write} methods use reflection which is slow.
This is ok for prototyping but has a serious performance impact.  In
each case, we know exactly what we're trying to write out, so we'll
allocate our own buffer and do the explicit conversion ourselves.

As an example of the performance improvement this makes, here are the
results from an (internal) benchmark:

benchmark          old ns/op    new ns/op    delta
BenchmarkDecode       427190       318845  -25.36%
deadcode--
improve test coverage
Merge pull request #6 from dgryski/improve-test-coverage

Improve test coverage
Merge pull request #5 from dgryski/remove-binary-read-write

Remove binary.{Read,Write} in favour of doing it by hand
Implement binunicode and long1
Merge upstream into my fork
Corrected comment to match function name
Removed debug message
And the other debug message...
Merge pull request #7 from JonPulfer/master

Implement binunicode and long1
Add .travis.yml
Implement the \x86 TUPLE2 opcode for decoding, operation 'Build a two-tuple
out of the top two items on the stack.'
Add test for opTuple2 decode
d.marker() doesn't seem to be the proper way to get stack length, use #'len on d.stack for #'loadTuple2 instead
Merge pull request #8 from Sean-Der/implement-tuple2-decode

Implement the TUPLE2 Opcode
Implement Tuple1 and Tuple3 opcodes.
Implement C GLOBAL opcode
Implement R REDUCE opcode
Export members for Class and Thunk struct