ripytide

I'm thinking mainly of types such as ```rust pub struct ToDoPerBackend(Vec); ``` Which might have to change to something like: ```rust pub struct TodoPerBackend(BTreeMap); // or pub struct TodoPerBackend(Vec) pub...

Or actually maybe even: ```rust pub struct TodoPerBackend { arch: Packages, debian: Packages, //etc.. }

Just FYI, I'm halfway-through some more refactors at the moment which may end up overhauling the Backend trait. You can see where I'm at on my [`rework2`](https://github.com/ripytide/pacdef/tree/rework2) branch. Hopefully I'll...

Here's another possible idea for improving the syntax, how about using lua? We could take inspiration from how the lazyvim package manager for neovim works, plus integrating lua with rust...

Good question, as far as I am aware I can recall two precedents for this kind of operation: cargo's `cargo add` and this nix issue: https://github.com/NixOS/nix/issues/3824. `cargo add` was possible...

In my experience testing is very specific to the project, algorithm heavy code favors unit and property testing since functions tend to be pure and deterministic. Libraries like this however,...

Could we keep this issue open so I can refer to it when working on the new review implementation along with #36?

Would the maintainers be open to merging this crate with the `imageproc` crate? That would help centralize a lot of the effort put into the two libraries.

I think blocks would be a better default since if you end up putting something really small in the block then `rustfmt` will usually remove the `{}`s which saves a...

I still think that rotations and flips are image processing operations and as such belong in `imageproc` and so should not be exposed from the `image` crate. But if they...