API Method Naming

[jordan-wright]

Nice job!!

I'd recommend renaming the API to allow a general io.Reader and io.Writer. Currently, you are forced to interact with on-disk files only. What if I want to write to a .tar.gz from a HTTP response body, etc.? Feel free to check the Reddit comments here for more on this.

I was faced with a similar problem with my email package. I resolved it by making Attach() (in your case Compress() and Extract()) take an io.Reader (or io.Writer) as the argument, and made a separate function, AttachFile(), which served as a convenience function.

So, I propose that you make Compress() and Extract() more general and allow any reader and writer, and make new functions, CompressFile() and ExtractFile() serve as convenience.

I understand that you're aiming for simplicity, but in this case much more flexibility comes with little sacrifice to usability. Just a thought.

Keep up the good work!

[walle]

Thank you for taking the time to add this issue, with a lot of background info.

Sounds like a good idea, I don't know if I will add this right now though. I will keep this issue open, and take a look at it next time I get a little time to work on side projects like this.

Yes, you keep up the good work you too!

[jordan-wright]

Sounds good - never hesitate to shoot me an email if I can help in any way.