diff options
| author | Noratrieb <48135649+Noratrieb@users.noreply.github.com> | 2024-10-17 19:34:04 +0200 |
|---|---|---|
| committer | Noratrieb <48135649+Noratrieb@users.noreply.github.com> | 2024-10-18 18:18:41 +0200 |
| commit | e78d78868a4c9a4e29a02f70ede75ca8cfd39bef (patch) | |
| tree | cccca1e65ec3d674c77ae67dd6ccd89ec0220c0d /src/tools | |
| parent | 3a85d3fa785d95a7b7bcf4f160b67bffba7afd4a (diff) | |
| download | rust-e78d78868a4c9a4e29a02f70ede75ca8cfd39bef.tar.gz rust-e78d78868a4c9a4e29a02f70ede75ca8cfd39bef.zip | |
Allow `#[deny(..)]` inside `#[forbid(..)]` as a no-op with a warning
Forbid cannot be overriden. When someome tries to do this anyways, it results in a hard error. That makes sense. Except it doesn't, because macros. Macros may reasonably use `#[deny]` in their expansion to assert that their expanded code follows the lint. This is doesn't work when the output gets expanded into a `forbid()` context. This is pretty silly, since both the macros and the code agree on the lint! Therefore, we allow `#[deny(..)]`ing a lint that's already forbidden, keeping the level at forbid.
Diffstat (limited to 'src/tools')
| -rw-r--r-- | src/tools/tidy/src/issues.txt | 1 |
1 files changed, 0 insertions, 1 deletions
diff --git a/src/tools/tidy/src/issues.txt b/src/tools/tidy/src/issues.txt index 22126674c15..97c42752c12 100644 --- a/src/tools/tidy/src/issues.txt +++ b/src/tools/tidy/src/issues.txt @@ -2758,7 +2758,6 @@ ui/lint/issue-63364.rs ui/lint/issue-70819-dont-override-forbid-in-same-scope.rs ui/lint/issue-79546-fuel-ice.rs ui/lint/issue-79744.rs -ui/lint/issue-80988.rs ui/lint/issue-81218.rs ui/lint/issue-83477.rs ui/lint/issue-87274-paren-parent.rs |