2 ms·
> For one, it’s common that you get different versions anyway (the Zola build currently has two versions each of unicase, parking_lot, parking_lot_core, crossbe
by geofft 7y ago
> For one, it’s common that you get different versions anyway (the Zola build currently has two versions each of unicase, parking_lot, parking_lot_core, crossbeam-deque, toml, derive_more, lock_api, scopeguard, and winapi).
This seems like a specific thing that would be a measurable win and a not uncommon problem (e.g., I have a test kernel module that doesn't have many dependencies, and it still has two generic-arrays, two proc-macro2s, and two unicode-xids). Is there something that could be done here technically, such as pull requests to bump common crates to using the same version of even-more-common dependencies?
- MaulingMonkey 7y ago> generic-array This is up to 0.13.2... plenty of supposedly breaking API churn, no wonder you have two copies. Yes, your dependencies probably rely on different 0.x versions, and a pull request could fix that. You can inspect your Cargo.lock file to figure out which ones are to blame. > Is there something that could be done here technically, such as pull requests to bump common crates to using the same version of even-more-common dependencies? Yep, that's the fix. README.md badges like https://deps.rs/repo/github/rust-lang/cargo https://deps.rs/repo/github/rust-lang/cargo can alert people to out-of-date dependencies. You can even automate some of the pull requests with something like https://github.com/marketplace/dependabot-preview https://github.com/marketplace/dependabot-preview if you control the repositories.