Support different lintcheck CARGO_TARGET_DIR env variables #14859
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
rustbot
added
the
S-waiting-on-review
dswij
approved these changes
May 21, 2025
|
Wait 1 single minute @dswij before merging, I think I have an improvement. (Using the same |
rust-cloud-vms
bot
force-pushed
the
better-target-lintcheck
branch
from
c6911a0 to
f1ad1cd
Compare
|
Ok, so I scraped the This makes comparing several different Clippy binaries via lintcheck heaps more comfortable. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Make lintcheck support different
CARGO_TARGET_DIR, do not hardcodetarget(useful for perf)changelog:none