cargo-component icon indicating copy to clipboard operation
cargo-component copied to clipboard

Confusing error if versions of local dependencies don't align

Open rylev opened this issue 1 year ago • 2 comments

In a wit file I was referring to a dependency wit package but forgot to attach a version to it. Naturally, resolution failed as I don't have an unversioned package with that name listed as a dependency. However, this was very confusing as the configuration in Cargo.toml doesn't use a version (when the dependency is local). Perhaps, the resolver could search for packages with the same name and different version when building the error message?

rylev avatar Feb 26 '24 19:02 rylev