Stream: git-wasmtime

Topic: wasmtime / issue #14274 Consider rusty_zstd for wasmtime-...

view this post on Zulip Wasmtime GitHub notifications bot (Sep 03 2026 at 17:02):

Ttimmahlax opened issue #14274:

The value of integrating

Wasmtime is a standalone WebAssembly runtime — Cranelift-backed compilation, fast instantiation, and a security-focused sandbox.

You compress compiled artifacts in the cache crate with the zstd crate; Cargo.toml pins zstd = "^0.13.0".

Swapping that layer for rusty_zstd removes the C toolchain from the cache path. No zstd-sys, no cc/libzstd build step, empty library dependency tree. Unsafe in the codec lives in one audited SIMD module. Compress and decompress stay covered, with dual-direction interop against facebook/zstd. The rusty_zstd README's size column is within ~2-4% of C across the level range. Cranelift, WASI, and the embedder API are untouched.

Not asking for a rip-and-replace.

How to integrate

Add rusty_zstd from crates.io to the cache crate's Cargo.toml. See the rusty_zstd README for the compress/decompress API rather than a guessed mapping from zstd.

A feature-flagged trial is the smallest path. Cache keys, invalidation, tests, and on-disk layout stay yours. Frames facebook/zstd already wrote still decode, and frames rusty_zstd emits still decode in facebook/zstd v1.5.7, per that README.

Remade With Rust & MATA

We are rebuilding the stack in safe Rust — codecs, parsers, compression, identity, storage — so projects can drop C dependencies without giving up performance. The rest of the org is at https://github.com/Remade-With-Rust if anything else fits the build. Close this issue if it is a poor fit.

view this post on Zulip Wasmtime GitHub notifications bot (Sep 10 2026 at 16:50):

fitzgen closed issue #14274:

The value of integrating

Wasmtime is a standalone WebAssembly runtime — Cranelift-backed compilation, fast instantiation, and a security-focused sandbox.

You compress compiled artifacts in the cache crate with the zstd crate; Cargo.toml pins zstd = "^0.13.0".

Swapping that layer for rusty_zstd removes the C toolchain from the cache path. No zstd-sys, no cc/libzstd build step, empty library dependency tree. Unsafe in the codec lives in one audited SIMD module. Compress and decompress stay covered, with dual-direction interop against facebook/zstd. The rusty_zstd README's size column is within ~2-4% of C across the level range. Cranelift, WASI, and the embedder API are untouched.

Not asking for a rip-and-replace.

How to integrate

Add rusty_zstd from crates.io to the cache crate's Cargo.toml. See the rusty_zstd README for the compress/decompress API rather than a guessed mapping from zstd.

A feature-flagged trial is the smallest path. Cache keys, invalidation, tests, and on-disk layout stay yours. Frames facebook/zstd already wrote still decode, and frames rusty_zstd emits still decode in facebook/zstd v1.5.7, per that README.

Remade With Rust & MATA

We are rebuilding the stack in safe Rust — codecs, parsers, compression, identity, storage — so projects can drop C dependencies without giving up performance. The rest of the org is at https://github.com/Remade-With-Rust if anything else fits the build. Close this issue if it is a poor fit.

Last updated: Sep 20 2026 at 18:08 UTC