Print globs when workspace members can't be found #15093
Merged
+28
−16
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Cargo expands globs when loading workspace members. If the glob happens to match some non-crate directory, it causes an error that may be tricky to understand, because it makes Cargo complain that it failed to read a
Cargo.toml
from a specific directory, but that directory name won't be listed explicitly anywhere inCargo.toml
, so it may seem that Cargo is trying to read some made-up phantom manifest.I've made the error messages mention which glob has been used to select the missing workspace member.