Volker Ströbel

One possibility to solve this, is to create your own `std::io::Read` alike Trait with a custom error type and implement this for everything implementing `std::io::Read` if std is available. This...

> Or even if you don't believe that pixels should be `Vec` elements, at least use an enum of `{Eight(Vec), Sixteen(Vec)}` with an element per channel, so that it doesn't...

Sorry for the late reply. I'm not against this kind of utilities, but I'm wondering how useful this is in the context of Rust. Feel free to send a PR...

Adding support for std::simd has been on my todo list for some time, too. I've create a WIP branch and pull request (#13) which only contains an optimized RGB to...

Wide is an interesting crate, especially before the stabilization of std::simd. What bothers me about integrating it is the following version policy: `The rust-version entry may increase in any new...

> MSRV bumps are no longer a concern now that our MSRV is above 1.85. > > Cargo has shipped the [Rust-version aware resolver](https://doc.rust-lang.org/edition-guide/rust-2024/cargo-resolver.html) and made it the default [in...

Just some random thoughts, but wouldn't it be better to expose the 8x8 nature of the blocks to the compiler by introducing a Block structure that is backed by an...