Alexandre Bury
Alexandre Bury
A zstd context is `Send` (you can move it across threads), but it is not `Sync` (you should not query it across threads). It was initially set in https://github.com/gyscos/zstd-rs/pull/32. One...
Hi, Not that I know of. This might be a question for https://github.com/facebook/zstd. It does sound surprising though. I wouldn't expect the zstd lib to have a stack usage that...
Might be related to the `parallel` feature we enable in `cc`?
Hi, and thanks for the report! I'm not entirely sure how to get bit-identical output with the CLI. First, you will of course need to ensure you are using the...
Note that most zst-compressed files are going to store a single frame (for optimal compression ratio). If you want to concatenate several frames and need random access to them, you...
Hi, and thanks for the PR! The comment from the zstd lib refers to internal buffers that need to be flushed: when no more input is required, but more output...
Ah I finally understood what happens: when it reaches the unexpected EOF, the `Decoder` returns an error. If you call it again, it will keep returning this same error. The...
Indeed, thanks for the report! Should now be fixed.
Oh right I only updated `Decompressor::decompress()`. Fixing that now.
Hi, and thanks for the report! I can look into adding a `no-wasm-shim` feature, but I'm curious why it's not working for you. `rust_zstd_wasm_shim_malloc` should be provided by the `zstd-sys`...