You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The change in rust-lang/cargo#12783 causes cargo to return lib package names which are different to the names obtained through cargo metadata. More specifically, the cargo name will use underscores (_) instead of dashes (-), otherwise they are the same.
We first noticed this discrepancy during a Rust toolchain upgrade in model-checking/kani#3102, where we worked around this issue by introducing a weaker comparison between the targets. cargo metadata was specifically mentioned in this comment from rust-lang/cargo#12783 as an area that would be affected.
What's the long-term plan to avoid the discrepancy? Does cargo metadata need to do the same replacement?
The text was updated successfully, but these errors were encountered:
We're only processing information that cargo provides to us. So if cargo sends us dashes, we'll report dashes, if cargo sends us underscores we'll report underscores.
cargo metadata is a built-in command in Cargo. cargo_metadata is a library parsing that JSON output. If you have questions about cargo metadata please file issues against rust-lang/cargo with detailed use cases and reproduction.
Understood, thank you for your comments! I'll close this issue and open another one in rustlang/cargo once I've collected more details about our use-case 😄
The change in rust-lang/cargo#12783 causes
cargo
to return lib package names which are different to the names obtained throughcargo metadata
. More specifically, thecargo
name will use underscores (_
) instead of dashes (-
), otherwise they are the same.We first noticed this discrepancy during a Rust toolchain upgrade in model-checking/kani#3102, where we worked around this issue by introducing a weaker comparison between the targets.
cargo metadata
was specifically mentioned in this comment from rust-lang/cargo#12783 as an area that would be affected.What's the long-term plan to avoid the discrepancy? Does
cargo metadata
need to do the same replacement?The text was updated successfully, but these errors were encountered: