-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
borrow_interior_mutable_const interacts poorly with the http crate #3825
Labels
C-bug
Category: Clippy is not doing the correct thing
Comments
This looks like the same or similar underlying cause as #3962, through a few layers of |
rail-rain
added a commit
to rail-rain/rust-clippy
that referenced
this issue
Oct 4, 2020
fix a false positive in two `interior_mutable_const` lints where a constant with enums gets linted even if it uses a clearly unfrozen variant. Note that the code uses the MIR interpreter, which the author of rust-lang#3962 thought unlikely to be a solution. This might be over-engineering; but, I think it's important to be able to work with the 'http' crate (rust-lang#3825).
rail-rain
added a commit
to rail-rain/rust-clippy
that referenced
this issue
Oct 4, 2020
fix a false positive in two `interior_mutable_const` lints where a constant with enums gets linted even if it uses a clearly unfrozen variant. Note that the code uses the MIR interpreter, which the author of rust-lang#3962 thought unlikely to be a solution. This might be over-engineering; but, I think it's important to be able to work with the 'http' crate (rust-lang#3825).
Ryan1729
pushed a commit
to Ryan1729/rust-clippy
that referenced
this issue
Nov 7, 2020
fix a false positive in two `interior_mutable_const` lints where a constant with enums gets linted even if it uses a clearly unfrozen variant. Note that the code uses the MIR interpreter, which the author of rust-lang#3962 thought unlikely to be a solution. This might be over-engineering; but, I think it's important to be able to work with the 'http' crate (rust-lang#3825).
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The http crate defines constants for common header names, but any use of them triggers this lint:
The text was updated successfully, but these errors were encountered: