diff options
| author | Matthias Krüger <matthias.krueger@famsik.de> | 2022-06-16 09:10:20 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2022-06-16 09:10:20 +0200 |
| commit | ac2b7a261c94d2d7d718bede54fc93c7f2fdd641 (patch) | |
| tree | e05a16e385c43dbd68050da55b016ec227354fcb /compiler/rustc_codegen_gcc | |
| parent | d03a547cad3ce8a3dc3b424156e0eec38475da1b (diff) | |
| parent | 76cbc1dae300a3c9edb07e5a59e91738d9d6027c (diff) | |
| download | rust-ac2b7a261c94d2d7d718bede54fc93c7f2fdd641.tar.gz rust-ac2b7a261c94d2d7d718bede54fc93c7f2fdd641.zip | |
Rollup merge of #97757 - xFrednet:rfc-2383-expect-with-force-warn, r=wesleywiser,flip1995
Support lint expectations for `--force-warn` lints (RFC 2383) Rustc has a `--force-warn` flag, which overrides lint level attributes and forces the diagnostics to always be warn. This means, that for lint expectations, the diagnostic can't be suppressed as usual. This also means that the expectation would not be fulfilled, even if a lint had been triggered in the expected scope. This PR now also tracks the expectation ID in the `ForceWarn` level. I've also made some minor adjustments, to possibly catch more bugs and make the whole implementation more robust. This will probably conflict with https://github.com/rust-lang/rust/pull/97718. That PR should ideally be reviewed and merged first. The conflict itself will be trivial to fix. --- r? `@wesleywiser` cc: `@flip1995` since you've helped with the initial review and also discussed this topic with me. :upside_down_face: Follow-up of: https://github.com/rust-lang/rust/pull/87835 Issue: https://github.com/rust-lang/rust/issues/85549 Yeah, and that's it.
Diffstat (limited to 'compiler/rustc_codegen_gcc')
0 files changed, 0 insertions, 0 deletions