Adam Hathcock

These are just convenance methods. You don't have to use them. You can write your own to write entries to whatever you like and however you like.

You might have stumbled on something because the file gets read and looks for a tar header.

I seemingly can't use that patch file Any chance of a PR?

modified the patch a little as my client corrupted it I think Please validate the PR

Probably cannot directly use nuget packages as not much is useful. Probably some code porting is required

Because I need access to a lot of the internals of archive formats and they don’t expose them. Otherwise, I’d love to.

I need to put some brain power to what the proper way is to implement async for streams. Often I see that there’s nothing really to do?

I meant more like if I use the async methods is that good enough? Would sync reuse the async code paths okay? Not sure at the moment.

Like if I only implement the async part of Streams, does it use that path if someone uses the sync part? I don’t want to have people use GetAwaiter().Result() or...

nope I'd probably just make everything async and let the Stream overloads (or provide them myself) async has been around long enough