pure-zstd/lib/pure_zstd.dart

/// A pure Dart zstd decompressor.
///
/// Decompression only, one RFC 8878 frame per call, on native platforms. It
/// refuses dictionaries and skippable frames; see the README for the rest.
library;

export 'src/decoder.dart' show ZstdDecoder, zstdDecode;
export 'src/exception.dart' show ZstdException;
Add a pure-Dart zstd decoder, as a benchmark A feasibility spike, standalone so it can move to its own repository. Not wired into the app and not a dependency of it. Decompression only, and only what our containers need: no dictionaries, no multi-frame, no streaming, and the content checksum is parsed but never verified. Native only, since the bit reader carries 56 bits in an int. It is correct on real data. The committed fixture decodes to the samples the generator wrote, and tool/oracle.py drives a byte-for-byte comparison against pyzstd over 32 containers and 2,615 blocks from both tiers, every thinned column count from 3601 to 361, and 88 S to 80 N. All identical. The numbers, AOT on this box, 131,072 bytes a block: 0.66 ms median against pyzstd's 0.175, so about 200 MB/s against 750. Across three tiles the range is 0.66 to 0.94 ms, and a 113 block sweep is 67 to 105 ms. The cost is the sequence loop and nothing else: a terrain block at level 19 carries around 1,700 literals and 14,400 sequences, so optimising the literal path bought nothing. 2026-09-21 21:37:56 -06:00			`/// A pure Dart zstd decompressor.`
			`///`
Document the public surface 2026-09-22 19:48:12 -06:00			`/// Decompression only, one RFC 8878 frame per call, on native platforms. It`
			`/// refuses dictionaries and skippable frames; see the README for the rest.`
Add a pure-Dart zstd decoder, as a benchmark A feasibility spike, standalone so it can move to its own repository. Not wired into the app and not a dependency of it. Decompression only, and only what our containers need: no dictionaries, no multi-frame, no streaming, and the content checksum is parsed but never verified. Native only, since the bit reader carries 56 bits in an int. It is correct on real data. The committed fixture decodes to the samples the generator wrote, and tool/oracle.py drives a byte-for-byte comparison against pyzstd over 32 containers and 2,615 blocks from both tiers, every thinned column count from 3601 to 361, and 88 S to 80 N. All identical. The numbers, AOT on this box, 131,072 bytes a block: 0.66 ms median against pyzstd's 0.175, so about 200 MB/s against 750. Across three tiles the range is 0.66 to 0.94 ms, and a 113 block sweep is 67 to 105 ms. The cost is the sequence loop and nothing else: a terrain block at level 19 carries around 1,700 literals and 14,400 sequences, so optimising the literal path bought nothing. 2026-09-21 21:37:56 -06:00			`library;`

			`export 'src/decoder.dart' show ZstdDecoder, zstdDecode;`
			`export 'src/exception.dart' show ZstdException;`