Binary project output within one workspace depends on build order

Multiple projects within a workspace overwrite each others output, if their executable have the same name.

Imagine the following Cargo.toml snippet to be part of two projects (referred to as project_aand project_b):

[[bin]]
name = "runner"
path = "src/main.rs"

When compiling the workspace after a change in project_a, the following command runs the executable from project_a:

cargo run -p project_b --bin runner

Problems

1. I expected the -p flag to be considered or to rise a warning that it's being ignored in conjunction with --bin
2. Cargo workspaces allow two projects to target the same binary name, but currently names must be unique within the workspace

Possible Solution(s)

1. Deprecate -p and --bin to be used in conjunction
2. Fail workspace build if two projects use the same binary-name

Notes
Output of cargo version:

cargo 1.48.0 (65cbdd2dc 2020-10-14)

Create a workspace with two projects whose Cargo.toml files define a binary named runner, then reproduce the behavior with cargo run -p project_b --bin runner. Trace Cargo's workspace binary selection and output handling; done means the requested project is selected reliably or Cargo reports the duplicate or conflicting configuration explicitly.