Felix Handte

My understanding matches, I think, what is being discussed here. Outside of `chunked` in HTTP/1.1, `TE` is little-used, and in practice `CE` has come to mean what `TE` was intended...

This is a really interesting idea, and it would be great to give users a tool to avoid this copy. My fundamental concern is that the `ZSTD_outBuffer` struct keeps a...

> Why is this a problem? It's certainly something we could disclaim in documentation, but I would *very strongly prefer* not to have the code lie about its contract with...

Ooh, interesting and tricky question. > a) Is it legal for the input to change during the call to compressStream2? ... no? I don't think it ever even occurred to...

Hi @boenrobot, I'm glad to hear this is something you're passionate about! I too really want to see this happen. Unfortunately, there are non-trivial challenges that have hindered progress. -...

In short, I am proposing that to start we add a CLI flag `--max-mem`. Ideally, it could take arguments of the form `x%`, and would limit zstd to using that...

@Cyan4973, see [here](https://github.com/facebook/zstd/blob/v1.5.1/lib/compress/zstd_compress.c#L2318-L2329) for an example of explicitly unpoisoning memory.

I thought about this a little bit and probably the simplest/best way to do this is to keep a known-initialized range. When the tag table is in that range, we...

The big question is whether we also want to get this in for 1.5.2.

> I think a sane approach would be to change the order that the cwksp stores elements. [...] Yeah, I guess so. The reason it was laid out this way...