-
-
Notifications
You must be signed in to change notification settings - Fork 14.9k
compiletest: Detect unused auxiliary crates? #133914
Copy link
Copy link
Open
Labels
A-compiletestArea: The compiletest test runnerArea: The compiletest test runnerC-enhancementCategory: An issue proposing an enhancement or a PR with one.Category: An issue proposing an enhancement or a PR with one.T-bootstrapRelevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap)Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap)
Metadata
Metadata
Assignees
Labels
A-compiletestArea: The compiletest test runnerArea: The compiletest test runnerC-enhancementCategory: An issue proposing an enhancement or a PR with one.Category: An issue proposing an enhancement or a PR with one.T-bootstrapRelevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap)Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap)
Type
Fields
Give feedbackNo fields configured for issues without a type.
There are some auxiliary crates that are unused in the
testsdirectory. I think it would be nice if compiletest could detect these and complain about them in some way.This might be difficult due to ignored tests, or tests that are otherwise not run, which don't load enough information to know which auxiliary tests are used.
If it ends up being technically challenging, perhaps someone could just manually go through and clean up the orphans?
I've been intending to do that, but just haven't been able to make the time.
Example: https://github.com/rust-lang/rust/blob/master/tests/ui/auxiliary/default-ty-param-cross-crate-crate.rs