diff options
| author | bors <bors@rust-lang.org> | 2020-12-13 16:37:31 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2020-12-13 16:37:31 +0000 |
| commit | 684f17e565594c8451ee588d77a3289dcc816a8a (patch) | |
| tree | 6187863f0c2347f5b70323e7968c7f32e3625080 /src/test/codegen/src-hash-algorithm | |
| parent | b7db5bfc50095c259d2f128ddb96f7faf8654e3c (diff) | |
| parent | f93d9654d2ce012e146b8dfa615ad724f4bb23fd (diff) | |
| download | rust-684f17e565594c8451ee588d77a3289dcc816a8a.tar.gz rust-684f17e565594c8451ee588d77a3289dcc816a8a.zip | |
Auto merge of #6441 - ebroto:use_rustflags, r=flip1995
Pass Clippy args also trough RUSTFLAGS
This removes a hack (\_\_CLIPPY_HACKERY\_\_) to add another one :)
It allows this workflow to work:
```terminal
cargo clippy # warning: empty `loop {}` wastes CPU cycles
cargo clippy -- -A clippy::empty_loop # no warnings emitted
```
Before this change the new flag was not taken into consideration in cargo's fingerprint and the warning was emitted again. I guess that ideally we could add a specific env var for compiler wrapper arguments, but in the meantime this should do the job.
changelog: Pass clippy arguments through RUSTFLAGS so that changing them will trigger a rebuild
r? `@flip1995`
cc `@ehuss` (I think this may count as another step towards stabilizing `RUSTC_WORKSPACE_WRAPPER` :smile:)
Fixes #5214 and avoids frustration for users unfamiliar with the issue
Diffstat (limited to 'src/test/codegen/src-hash-algorithm')
0 files changed, 0 insertions, 0 deletions