3 ms·

It’d be nice if they at least mentioned the existing pure rust implementation. https://github.com/KillingSpark/zstd-rs https://github.com/KillingSpark/zstd-rs

by ikawe 4mo ago

It’d be nice if they at least mentioned the existing pure rust implementation. https://github.com/KillingSpark/zstd-rs https://github.com/KillingSpark/zstd-rs And better yet if they compared it explicitly in their “why” section. As it is, I’m left guessing.

merlincorey 4mo ago
The "Why" section exclusively opens with a reference to zstd-rs: > Why though? > Using zstd in Rust is already supported via the zstd crate, so why bother with a whole new implementation? Separately, I'd say their end goal seems to be replacing the C library dependency in Rust's zstd-rs: > We have our own fork of the zstd that uses libzstd-rs-sys instead of the C library. We'd like to upstream this at some point.
- soulbadguy 4mo ago
  They seems to be referering to https://github.com/gyscos/zstd-rs https://github.com/gyscos/zstd-rs which looks like a wrapper around the C library. https://github.com/KillingSpark/zstd-rs https://github.com/KillingSpark/zstd-rs. is a pure rust implementation