diff options
| author | Dylan DPC <99973273+Dylan-DPC@users.noreply.github.com> | 2022-03-03 01:09:12 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2022-03-03 01:09:12 +0100 |
| commit | 493ed7a6af1dbd8fe06f70add0a6814f79f35f5c (patch) | |
| tree | 07ad9807526b07b6cb2ae84b740edc6863c6017d /compiler/rustc_codegen_llvm/src/context.rs | |
| parent | 7537b2036a472e80fce4295eb799a53f61f959c0 (diff) | |
| parent | 765205b9b8274f6437d3fee291bc80e7e61a0af0 (diff) | |
| download | rust-493ed7a6af1dbd8fe06f70add0a6814f79f35f5c.tar.gz rust-493ed7a6af1dbd8fe06f70add0a6814f79f35f5c.zip | |
Rollup merge of #94433 - Urgau:check-cfg-allowness, r=petrochenkov
Improve allowness of the unexpected_cfgs lint This pull-request improve the allowness (`#[allow(...)]`) of the `unexpected_cfgs` lint. Before this PR only crate level `#![allow(unexpected_cfgs)]` worked, now with this PR it also work when put around `cfg!` or if it is in a upper level. Making it work ~for the attributes `cfg`, `cfg_attr`, ...~ for the same level is awkward as the current code is design to give "Some parent node that is close to this macro call" (cf. https://doc.rust-lang.org/nightly/nightly-rustc/rustc_expand/base/struct.ExpansionData.html) meaning that allow on the same line as an attribute won't work. I'm note even sure if this would be possible. Found while working on https://github.com/rust-lang/rust/pull/94298. r? ````````@petrochenkov````````
Diffstat (limited to 'compiler/rustc_codegen_llvm/src/context.rs')
0 files changed, 0 insertions, 0 deletions