diff options
| author | bors <bors@rust-lang.org> | 2021-07-24 13:19:17 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2021-07-24 13:19:17 +0000 |
| commit | 18840b0719aa766a1bc49ea2eb5dc2e4cde7da3f (patch) | |
| tree | 5a2a6030e2f632bb5e06d57e6475c7b7074e3988 /compiler/rustc_data_structures/src | |
| parent | f9b95f92c8af07a24a870e5f6117aa5dfcee5f17 (diff) | |
| parent | b41672eba8b0f06d2803cbd3bc2bd9ca7a8f2465 (diff) | |
| download | rust-18840b0719aa766a1bc49ea2eb5dc2e4cde7da3f.tar.gz rust-18840b0719aa766a1bc49ea2eb5dc2e4cde7da3f.zip | |
Auto merge of #87296 - Aaron1011:inert-warn, r=petrochenkov
Warn on inert attributes used on bang macro invocation
These attributes are currently discarded.
This may change in the future (see #63221), but for now,
placing inert attributes on a macro invocation does nothing,
so we should warn users about it.
Technically, it's possible for there to be attribute macro
on the same macro invocation (or at a higher scope), which
inspects the inert attribute. For example:
```rust
#[look_for_inline_attr]
#[inline]
my_macro!()
#[look_for_nested_inline]
mod foo { #[inline] my_macro!() }
```
However, this would be a very strange thing to do.
Anyone running into this can manually suppress the warning.
Diffstat (limited to 'compiler/rustc_data_structures/src')
0 files changed, 0 insertions, 0 deletions
