diff options
| author | bors <bors@rust-lang.org> | 2021-08-16 00:20:31 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2021-08-16 00:20:31 +0000 |
| commit | d4e2fcabb1cd69ecea19c6f8503ca86a34a183ec (patch) | |
| tree | 03d240dc6939a239c7b5cac57c9417f641816fd6 /src/test/codegen/src-hash-algorithm | |
| parent | 5449e23e671c500458ba70f5890fc5caa2853845 (diff) | |
| parent | 997ddbbfd8adf3a56307c817d562fc6d07bcbd6c (diff) | |
| download | rust-d4e2fcabb1cd69ecea19c6f8503ca86a34a183ec.tar.gz rust-d4e2fcabb1cd69ecea19c6f8503ca86a34a183ec.zip | |
Auto merge of #7521 - rukai:fix_lintcheck_local_path_handling, r=camsteffen
lintcheck always copies in a fresh crate when provided with a crate path changelog: none When lintcheck is run on local crates it copies the crate to `target/lintcheck/sources/crate_name` on the first run only. Then in subsequent runs of lintcheck it reuses this same copy. This caching behaviour makes sense when dealing with immutable crates.io releases and git commits. However it is quite surprising that the changes to my local crate are not used when I run lintcheck. To fix this I removed the copy, instead clippy runs directly off the provided crate folder. I have tested this and have not observed any negative effects from doing this. But maybe i'm missing something as im not familiar with clippy! Alternatively we could make it copy the entire crate every run, but that seems problematic to me as multi-gigabyte target folders will take a long time to copy and wear down SSDs for developers who frequently run lintcheck.
Diffstat (limited to 'src/test/codegen/src-hash-algorithm')
0 files changed, 0 insertions, 0 deletions