oyvindln

At least for the compression side, if I understand the RFC correctly, you need to ensure there is an empty block at the end, and then remove the last 4...

If the only parts of libc used are the C data types, it's possible you could do a temporary workaround using a cut-down version of libc or similar (not sure...

Yeah it seems reasonable to have something like this for cases where flate2 is too heavy. I've not personally done much work on this library in quite a while, might...

The use of [Alternative operatos](https://en.cppreference.com/w/cpp/language/operator_alternative) (```or``` and ```and``` instead of ```||``` and ```&&```) in the code also requires extra compiler definitions or headers which isn't ideal either.

For the rust back-end we shouldn't really need to be using unsafe stuff unless there is some very good reason for it. Not sure if say avoiding zero-initializing a vector...

compress_vec and decompress_vec functions are really just convenience wrappers for using ```compress```/```decompress``` which operates on a slice with Vecs wrapping some unsafe code to use the allocated unused capacity of...

Hm. I don't know whether this is an issue or not. There aren't really any alternatives atm as simd-adler32 uses unsafe (due to the use of manual SIMD code) hence...

Something in the signal causes the vsync serration algorithm to interpret something as vertical sync that isn't, and detect the completely wrong levels, and something with the fallback/failsafe logic is...

We probably also don't need it to process at 40 mhz

Another thing that seems to take up a bit of time is concatenating the input/output arrays in demodcache. When reading from file it reads into a list of blocks (arrays)...