There was no breaking changes in version 0.10.0.0,
so let's also release under 0.8.6.0.

GHC gave a warning that we needed modules but didn't explicitly depend
on them in the .cabal file.

Same as version 0.9.0.0. There were no new breaking changes, so let's
go back to major 0.8.

See #123.

Now that Generics is used in all targets, we also need ghc-prim.

The dependency problem should have been fixed now.
See haskell/tar#15.

This CPP is no longer needed now that we only support GHC >= 7.4.

Next version won't be 0.9.0.0 as previously stated. Looks like no changes
should be breaking, except for the semi public API in
Data.Binary.Builder.Internal which now has been removed.

Also remove GHC 7.6.3 from 'tested-with'. It was removed from Travis CI since
its dependencies doesn't build.

This fixes #105. Older GHC versions + clang ran into trouble, which this commit
fixes.

PVP said 0.9.0.0 was not required.

Let's share the address space with a malevolent agent of chaos.

This is so that we can write and read things like [Void], or (Expr Void)
- something I'm actually doing in Morte.

https://github.com/Gabriel439/Haskell-Morte-Library/pull/26

The reader always fails if you actually try to get an instance of it.
Trying to access a void value should not happen for well-formed
instances, for example:

    *Data.Binary Data.Void> decode $ encode ([] :: [Void]) :: [Void]
    []

We use Cabal's PackageDescription as the type to serialize. It is large,
has many levels of data types, and also uses enums and strings. It's a
good stress test.

GenericsBench defines criterion benchmarks for serialization and
deserialization.

In GenericsBenchTypes we derive the Binary instances. PackageDescription
already defines Binary instances for the system installed Binary, but
naturally this won't work for the benchmark - we need our own instances
that are derived from the code in this library.

The data to serialize we get from your
.cabal/package/hackage.haskell.org/ directory, it's data from hackage,
not autogenerated.
GenericsBenchCache makes sure that if we rerun the benchmark we will use
the same PackageDescriptions, even if the user has executed
'cabal update' since the last benchmark run.