GitLab

No idea why we need this, but go 1.16 doesn't always completely GC the
first round.

fixes #3

So, creating interfaces *allocates*. That means `pool.Put([]byte)` allocates,
that's obviously bad. This was, unfortunately, showing up in go-ipfs after
switching to a pool-backed yamux.

What's the solution to too many allocations? More object pools!

They won't use the buffer pool but it doesn't hurt to be nice to the user by
allocating such slices anyways.

Before, this library assumed that we wanted to use pools for things other than
byte slices. In practice, this isn't the case and supporting such use-cases made
this library annoying to use.

This way, copying it won't copy the underlying pool.

Also, initialize it immediately instead of in an `init` function to ensure that
it's fully initialized immediately.

Per the documentation, this example *isn't* guaranteed to work (and, in
practice, it fails occasionally).