everything in the title :)

Howdy and thanks for a awesome library!

We have a use case where we tar up a path and upload it to google cloud storage, which takes a []byte as the object you wish to upload. Later on we might download the tar which again gives us a []byte and untar it to some path.

In v2.0.1 we have the super helpful

Compress(sourceDir string) (tar []byte, err error)
Uncompress(destinationDir st

The restore --target-action documentation states:

This option is effective when hot_standby=on is configured in postgresql.conf, otherwise the cluster will be promoted when the target is reached or there is no more WAL in the archive.

However, I don't believe this is accurate. In recent versi

When using

./lzbench -r -elz4 ../corpus/silesia

To run against a directory, memcpy only runs once:

lzbench 1.5 (64-bit Linux)   Assembled by P.Skibinski
Compressor name         Compress. Decompress. Compr. size  Ratio Filename
memcpy                  11571 MB/s 11643 MB/s    10192446 100.00 ../corpus/silesia/dickens
lz4 1.7.3                 267 MB/s  1830 MB/s     642874

It should be quite obvious for first time users to see some simplest APIs (to compress/uncompress buffer without dealing with any file io). Strangely, lizard has links to file format, but no clues to basic api use (is it in examples, which one is the "hello world"?. I've been using zlib for more than a decade, and I've never needed to know its file format, perhaps same for 90% of its users.

IMO

The streams module currently only supports the double buffer approach, and not the ring buffer approach. The scaffolding for supporting the double buffer approach is in the code, however. This just needs a willing volunteer to implement it.

The streams module was authored by @tSed who may be able to give guidance to a volunteer.