Consume z.current prepared by Reader.Read in Reader.WriteTo (#50)

... to fix missing data when WriteTo is called after Read.

Signed-off-by: Miloslav Trmač <[email protected]>

Signed-off-by: Miloslav Trmač <[email protected]>

reader: Fix missing buffers (#35)

When resetting before reading all content temporary buffers were lost.

Make sure to re-add temporary buffers.

Fixes #34

Never return negative values from `Write`, as they can panic in `bufi…

…o` (#33)

* Never return negative values from `Write`, as they can panic in `bufio`

pgzip: Fix an occasional segfault/panic with pgzip (#30)

This change fixes a occasional (5-10 out of 1000 test runs) segfault/panic on
sync.Pool struct access. Basically what happens there is that the original code
assigns a zero-value sync.Pool struct to the existing z.dstPool variable.
In general this kind of assignment is safe only if object is not used anymore /
in parallel by anything else. While is kind of true in a sense that none of the
goroutines are using it, in case of sync.Pool the garbage collector does
special management of the data with weak references and in right weather
conditions corrupts internal state (more precisely the sync.Pool.local might
become nil before reading it but after reading a nonzero sync.Pool.localSize;
leading to invalid memory reference in sync.Pool.Get() ).

godoc: added new Default values for SetConcurrency (#29)

it seems that the default was changed and the function documentation was wrong

v1.2.0

Merge pull request #14 from klauspost/fix-truncated-gzip-input

Fix truncated gzip input

Merge pull request #12 from klauspost/rewrite-error-handling

Rewrite error handling