I'm starting to wonder if implementing this in cargo itself would be the easiest path to success. My ideal vision would be "what's the simplest change I can make to make it so we're only using one version of this crate?" I think within cargo you could do speculative resolution.
-
-
Prikaži ovu nitHvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
-
-
Cargo udeps can find unused dependencies: https://crates.io/crates/cargo-udeps …
-
Most of my problems seem to be "I depend on crate A, which depends on crate B, which depends on an old version of crate C".
Kraj razgovora
Novi razgovor -
-
-
https://crates.io/crates/guppy is the answer :D
-
Ohh! Fascinating! I will give that a shot!
- Još 2 druga odgovora
Novi razgovor -
-
-
cargo-tree is the basic one, but cargo-guppy can be made to give you really useful information too (like what you need to touch to update an old dep)
-
Guppy is quite powerful. cc/
@sunshowers6
Kraj razgovora
Novi razgovor -
-
-
I just look at cargo.lock file, with a bit of effort you can see what depends on what. But its pretty bad UX
-
"cargo tree" helps with that!
Kraj razgovora
Novi razgovor -
Čini se da učitavanje traje već neko vrijeme.
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.