-
Notifications
You must be signed in to change notification settings - Fork 1.7k
undocumented_unsafe_blocks doesn't detect safety comment above associated constant #11709
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Labels
C-bug
Category: Clippy is not doing the correct thing
I-false-positive
Issue: The lint was triggered on code it shouldn't have
Comments
@rustbot claim |
@rustbot claim |
profetia
added a commit
to profetia/rust-clippy
that referenced
this issue
Feb 17, 2025
profetia
added a commit
to profetia/rust-clippy
that referenced
this issue
Feb 23, 2025
profetia
added a commit
to profetia/rust-clippy
that referenced
this issue
Mar 1, 2025
github-merge-queue bot
pushed a commit
that referenced
this issue
Mar 1, 2025
fixes #11709 Continuation of #12672. r? @Alexendoo if you don't mind? changelog: [`undocumented_unsafe_blocks`] fix FP on trait/impl items
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
Labels
C-bug
Category: Clippy is not doing the correct thing
I-false-positive
Issue: The lint was triggered on code it shouldn't have
Uh oh!
There was an error while loading. Please reload this page.
Summary
I make use of the
voladdress
crate which uses a pattern of "unsafe construction, safe use", but when I put aVolAddress
in a constant clippy doesn't detect the safety comment I add above it.Reproducer
I tried this code:
I expected to see this happen:
no clippy warning
Instead, this happened:
a clippy warning
Version
Additional Labels
No response
The text was updated successfully, but these errors were encountered: