Grzegorz MartensandClaude Opus 5.5 05300ea5bc M2.6: say what was measured, not why, and test the other block zlib-rs refuses ...

The Claims review of the branch: the docs said miniz_oxide "builds a block's
tables for every block", which a timing doesn't show. They now say what was
timed: about 1.7 us for every fixed-Huffman block, empty or not. "The worst
comes to about 7 ns a step" was per byte read; a stage's start, about 0.25 us
under zlib-rs (1.6 us for eight over an empty stream, release), isn't priced,
since every way to repeat one takes bytes of the file. The letterhead test's
doc promised more than it checks.

The same review found a second shape zlib-rs refuses where miniz_oxide read
on: a dynamic block whose code has no end-of-block symbol. flate.rs's quirks
and the README row say so, and a_dynamic_code_without_an_end_is_damage checks
that nothing of it is kept.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01AmsdeUCdTaD72jkDw2pJKY

2026-11-03 00:14:52 +01:00

..

jbig2

M2.6: images decode outside the renderer only through an ImageBudget

2026-11-02 14:24:21 +01:00

ascii85.rs

…

asciihex.rs

…

ccitt.rs

M2.6: images decode outside the renderer only through an ImageBudget

2026-11-02 14:24:21 +01:00

flate.rs

M2.6: say what was measured, not why, and test the other block zlib-rs refuses

2026-11-03 00:14:52 +01:00

jbig2.rs

M2.6: images decode outside the renderer only through an ImageBudget

2026-11-02 14:24:21 +01:00

lib.rs

M2.6: say what was measured, not why, and test the other block zlib-rs refuses

2026-11-03 00:14:52 +01:00

lzw.rs

…

mq.rs

M11: lossless JBIG2 for black-and-white images

2026-10-29 20:47:45 +01:00

predictor.rs

…

runlength.rs

…