> so i wrote a gzip decompressor from scratch<p>After skimming through the author's Rust code, it appears to be a fairly straightforward port of puff.c (included in the zlib source): <a href="https://github.com/madler/zlib/blob/develop/contrib/puff/puff.c" rel="nofollow">https://github.com/madler/zlib/blob/develop/contrib/puff/puf...</a>
The function<p><pre><code> fn bits(&mut self, need: i32) -> i32 { ....
</code></pre>
Put me in mind of one of my early experiments in Rust. It would be interesting to compare a iterator based form that just called .take(need)<p>I haven't written a lot of Rust, but one thing I did was to write an iterator that took an iterator of bytes as input and provided bits as output. Then used an iterator that gave bytes from a block of memory.<p>It was mostly as a test to see how much high level abstraction left an imprint on the compiled code.<p>The dissasembly showed it pulling in 32 bits at a time and shifting out the bits pretty much the same way I would have written in ASM.<p>I was quite impressed. Although I tested it was working by counting the bits and someone critizised it for not using popcount, so I guess you can't have everything.
<i>> I tested it was working by counting the bits and someone critizised it for not using popcount</i><p>PSA: Rust exposes the popcnt intrinsic via the `count_ones` method on integer types: <a href="https://doc.rust-lang.org/std/primitive.u32.html#method.count_ones" rel="nofollow">https://doc.rust-lang.org/std/primitive.u32.html#method.coun...</a>
I had a similar experience implementing simd instructions in my emulator, where I needed to break apart a 64-bit value into four eight-bit values, do an operation on each value, then pack it back together. My first implementation did it with all the bit shifts you’d expect, but my second one used two helpers to unpack into an array, map on the array to a second array, and pack the array again. The optimized output was basically the same.
Just like that author, many years ago, I went through the process of understanding the DEFLATE compression standard and producing a short and concise decompressor for gzip+DEFLATE. Here are the resources I published as a result of that exploration:<p>* <a href="https://www.nayuki.io/page/deflate-specification-v1-3-html" rel="nofollow">https://www.nayuki.io/page/deflate-specification-v1-3-html</a><p>* <a href="https://www.nayuki.io/page/simple-deflate-decompressor" rel="nofollow">https://www.nayuki.io/page/simple-deflate-decompressor</a><p>* <a href="https://github.com/nayuki/Simple-DEFLATE-decompressor" rel="nofollow">https://github.com/nayuki/Simple-DEFLATE-decompressor</a>
>the only flag we care about is FNAME
The specification does not define an encoding for the file name. Different file systems may impose restrictions on certain names, so FNAME should not be used.
> twenty five thousand lines of pure C not counting CMake files. ...<p>Keep in mind this is also 31 years of cruft and lord knows what.<p>Plan 9 gzip is 738 lines total:<p><pre><code> gzip.c 217 lines
gzip.h 40 lines
zip.c 398 lines
zip.h 83 lines
</code></pre>
Even the zipfs file server that mounts zip files as file systems is 391 lines.<p>edit - post a link to said code: <a href="https://github.com/9front/9front/tree/front/sys/src/cmd/gzip" rel="nofollow">https://github.com/9front/9front/tree/front/sys/src/cmd/gzip</a><p>> ... (and whenever working with C always keep in mind that C stands for CVE).<p>Sigh.
You forgot to include <a href="https://github.com/9front/9front/tree/front/sys/src/libflate" rel="nofollow">https://github.com/9front/9front/tree/front/sys/src/libflate</a> which gzip is built around, which brings it closer to 10k lines.
His also omits CRC, which is part of the 25k lines, no --fast/--best/etc, missing some output formats, and so on. I'm sure the 25k includes a lot of bloat, but the comparison is odd. Comparing to your list would make much more sense.
I would expect a CRC to add a negligible number of lines of code. The reason that production-grade decompressors are tens of thousands of LOC is likely attributable to extreme manual optimization. For example, I wouldn't be surprised if a measurable fraction of those lines are actually inline assembly.
True. A most basic CRC implementation is about 7 lines of code: (presented in Java to avoid some C/C++ footguns)<p><pre><code> int crc32(byte[] data) {
int crc = ~0;
for (byte b : data) {
crc ^= b & 0xFF;
for (int i = 0; i < 8; i++)
crc = (crc >>> 1) ^ ((crc & 1) * 0xEDB88320);
}
return ~crc;
}
</code></pre>
Or smooshed down slightly (with caveats):<p><pre><code> int crc32(byte[] data) {
int crc = ~0;
for (int i = 0; i < data.length * 8; i++) {
crc ^= (data[i / 8] >> (i % 8)) & 1;
crc = (crc >>> 1) ^ ((crc & 1) * 0xEDB88320);
}
return ~crc;
}
</code></pre>
But one reason that many CRC implementations are large is because they include a pre-computed table of 256× 32-bit constants so that one byte can processed at a time. For example: <a href="https://github.com/madler/zlib/blob/7cdaaa09095e9266dee21314599a9258db53685e/crc32.h" rel="nofollow">https://github.com/madler/zlib/blob/7cdaaa09095e9266dee21314...</a>
That's java code, though... bit weird, esp. i % 8 (which is just i & 7). The compiler should be able to optimize it since 'i' is guaranteed to be non-negative, still awkward.<p>Java CRC32 nowadays uses intrinsics and avx128 for crc32.
Doesn't need to be inline assembly, just pre-encoded lookup tables and intrinsics-based vectorized CRC alone will add quite a lot of code. Most multi-platform CRC algorithms tend to have at least a few paths for byte/word/dword at a time, hardware CRC, and hardware GF(2) multiply. It's not really extreme optimization, just better algorithms to match better hardware capabilities.<p>The Huffman decoding implementation is also bigger in production implementations for both speed and error checking. Two Huffman trees need to be exactly complete <i>except</i> in the special case of a single code, and in most cases they are flattened to two-level tables for speed (though the latest desktop CPUs have enough L1 cache to use single-level).<p>Finally, the LZ copy typically has special cases added for using wider than byte copies for non-overlapping, non-wrapping runs. This is a significant decoding speed optimization.
Yes, there's subdirs with language bindings for many non-C langs, an examples folder with example C code, win32 specific C code, test code, etc.<p>More reasons it's an odd comparison.
gzip also contains a significant amount of compatibility code for different platforms.
Crc32 can be written in handful lines of code. Although it'd be better to use the vector instruction set - e.g. AVX when available.
But probably without any error checking.<p>Feels like Rust culture inherited "throw and forget" as an error handling "strategy" from Java<p>Sigh.
Hehe, why "probably"? It says "250 lines" right there in the subject. Surely one can skim the single file of code (<a href="https://github.com/ieviev/mini-gzip/blob/main/src/main.rs" rel="nofollow">https://github.com/ieviev/mini-gzip/blob/main/src/main.rs</a>) and offer criticism that isn't based on hypotheticals?<p>Anyway, I skimmed the file for you this time, and basically you're either correct or wrong, depending on your definition of "error checking." The code handles error conditions by aborting the process. Seeing as it's a standalone CLI program and not a library meant for reuse, safely shutting down with a meaningful message sounds like fair game to me.
This is an educational project. Not something for production. The article even says so!<p>You can leave the snide comments about “Rust culture” (whatever that is) out next time.
Why people ascribe error handling practices to languages is baffling. What language <i>doesn't</i> allow punting error handling until later? Even Haskell has "panic" functionality that fudges the type constraints to allow this.
EAFP is an explicit part of what makes code "pythonic", and the Zen of Python (`import this`) has the lines "Errors should never pass silently.
Unless explicitly silenced." Java has checked and unchecked exceptions. Rust has panics and Result<T, E>, and the ? operator.<p>The way a language's community handles errors and how the language itself handles errors are different things, sure, but they're not independent of each other.<p>That said, OP's snark against Rust is completely unmerited, and they can take my `impl From<OtherErr> for MyErr` from my cold dead hands.
Another dev who doesn’t show respect to what has been done and expect a particular language will do wonders for him. Also I don’t see this is much better in term of readability.
Where do you see the lack of respect? The author wanted to learn how gzip works and chose to implement it in a language they like to do so. As a learning tool, not because the world needs another gzip decompressor.
he does mention <a href="https://github.com/trifectatechfoundation/zlib-rs" rel="nofollow">https://github.com/trifectatechfoundation/zlib-rs</a> not just <a href="https://github.com/madler/zlib" rel="nofollow">https://github.com/madler/zlib</a>, but it would be interesting to hear from those developers also