diff options
| author | Matthias Krüger <matthias.krueger@famsik.de> | 2024-10-20 16:54:08 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-10-20 16:54:08 +0200 |
| commit | 7b714d4735c50a5148f30261a3e5e8e00807d8a8 (patch) | |
| tree | a3fd12362e2a2d3e648dc5850b7f8d1c3bb8f2d3 /tests/rustdoc-js-std/parser-errors.js | |
| parent | bfab34af4c5bfbcc9168064857bbec826a60a0b9 (diff) | |
| parent | 1af9d11583ea7ce06f78594b7f15bb0ba8bb22b1 (diff) | |
| download | rust-7b714d4735c50a5148f30261a3e5e8e00807d8a8.tar.gz rust-7b714d4735c50a5148f30261a3e5e8e00807d8a8.zip | |
Rollup merge of #121560 - Noratrieb:stop-lint-macro-nonsense, r=jieyouxu
Allow `#[deny]` inside `#[forbid]` as a no-op 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]` (or `#[warn]` for an allow-by-default lint) 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! By making it a warning instead, we remove the problem with the macro, which is now nothing as warnings are suppressed in macro expanded code, while still telling users that something is up. fixes #121483
Diffstat (limited to 'tests/rustdoc-js-std/parser-errors.js')
0 files changed, 0 insertions, 0 deletions
