fishfolk
Prune Dependencies Where Possible
We're currently running at ~581 dependencies for a build of Jumpy on Linux, which is quite a lot.
Lots of it is unavoidable, but we also have several duplicate dependencies detected by cargo deny check ban, which we might be able to eliminate.
We should try to prune our dependency tree as much as we can without causing adverse side-effects, just to keep things tidy as possible, and to reduce clean compile times, which can sometimes be off-putting to new contributors, and at the very least, add lead-in time when first jumping into jumpy development :wink:.
Good idea, I hadn't run it recently. I just tried it now and it says all dependencies appear to be used.
Ah, cargo machete found some "unused" deps, though. They were technically used somewhere in our dependency tree, but not directly used by the crate itself.
So it didn't help remove dependencies per-se, but it did find entries that we could harmlessly remove from our Cargo.toml.