about summary refs log tree commit diff
path: root/tests/rustdoc-js-std/parser-errors.js
diff options
context:
space:
mode:
authorNoratrieb <48135649+Noratrieb@users.noreply.github.com>2024-10-17 19:34:04 +0200
committerNoratrieb <48135649+Noratrieb@users.noreply.github.com>2024-10-18 18:18:41 +0200
commite78d78868a4c9a4e29a02f70ede75ca8cfd39bef (patch)
treecccca1e65ec3d674c77ae67dd6ccd89ec0220c0d /tests/rustdoc-js-std/parser-errors.js
parent3a85d3fa785d95a7b7bcf4f160b67bffba7afd4a (diff)
downloadrust-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 'tests/rustdoc-js-std/parser-errors.js')
0 files changed, 0 insertions, 0 deletions