first-crate and second-crate are the crates for each contests.
In first-crate (or second-crate), when I execute cargo equip --bin a, the following result appears.
error: multiple bin targets named `a` in this workspace
On the other hand, cargo run --bin a and cargo build --bin a succeed.
Is this expected behavior ?
If not, I would like suggest the following change
change workspace::targets_in_ws's return value to the targets in Metadata::root_package()
It seems that cargo run selects the targets in the current package, if neither --package, --exclude, --workspace nor --all flags are specified.
Since cargo-equip does not have these flags, I believe the natural behavior would be to select targets only from the current package rather than scanning all members in the workspace.
I always use cargo-eqiup for competitive programming contests.
I want to make the following workspace
first-crate
andsecond-crate
are the crates for each contests.In first-crate (or second-crate), when I execute
cargo equip --bin a
, the following result appears.On the other hand,
cargo run --bin a
andcargo build --bin a
succeed.Is this expected behavior ?
If not, I would like suggest the following change
workspace::targets_in_ws
's return value to the targets inMetadata::root_package()
It seems that
cargo run
selects the targets in the current package, if neither--package
,--exclude
,--workspace
nor--all
flags are specified.Since
cargo-equip
does not have these flags, I believe the natural behavior would be to select targets only from the current package rather than scanning all members in the workspace.Thank you for your confirming.
Best Regard.
My Environment