diff options
| author | bors <bors@rust-lang.org> | 2020-08-26 16:38:58 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2020-08-26 16:38:58 +0000 |
| commit | 1f2dd3b56aec4d8f97eb0b0552c166ef549d3316 (patch) | |
| tree | 4d026d8391b8cdaa7304a2a7ec1dada75278f2c3 /compiler/rustc_llvm/llvm-wrapper/CoverageMappingWrapper.cpp | |
| parent | 6ead62235a50e43b08a103d403d6fbfbc2b48352 (diff) | |
| parent | e11b3ee742ff5e5163ae6123a37f9fa757804842 (diff) | |
| download | rust-1f2dd3b56aec4d8f97eb0b0552c166ef549d3316.tar.gz rust-1f2dd3b56aec4d8f97eb0b0552c166ef549d3316.zip | |
Auto merge of #75903 - jyn514:lint-refactor, r=GuillaumeGomez
Warn about unknown or renamed lints in rustdoc Fixes https://github.com/rust-lang/rust/issues/75884. This is best reviewed one commit at a time. r? @GuillaumeGomez Originally I tried to do a much broader refactoring that got rid of `init_lints` altogether. My reasoning is that now the lints aren't being run anymore (after https://github.com/rust-lang/rust/pull/73566), there's no need to ignore them explicitly. But it seems there are still some lints that aren't affected by setting `lint_mod` to a no-op: ``` deny(pub_use_of_private_extern_crate) deny(const_err) warn(unused_imports) ``` (there are possibly more, these are just the ones that failed in the rustdoc test suite). Some of these seem like we really should be warning about, but that's a much larger change and I don't propose to make it here. So for the time being, this just adds the `unknown_lints` and `renamed_or_removed_lints` passes to the list of lints rustdoc warns about.
Diffstat (limited to 'compiler/rustc_llvm/llvm-wrapper/CoverageMappingWrapper.cpp')
0 files changed, 0 insertions, 0 deletions
