-
Notifications
You must be signed in to change notification settings - Fork 13.4k
Error on constant pointer dereference #6991
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
E-needs-test
Call for participation: An issue has been fixed and does not reproduce, but no test has been added.
I-ICE
Issue: The compiler panicked, giving an Internal Compilation Error (ICE) ❄️
Comments
Especially with |
Triage: still a bug; dereferencing in constant expressions does seem a little peculiar. |
Defining the semantics of constant expressions continues to be something we really should tackle. See also #5551. |
Triage bump, carry on. |
No longer valid. |
Flagging as needstest |
flip1995
pushed a commit
to flip1995/rust
that referenced
this issue
Apr 8, 2021
redundant_pattern_matching: look inside Refs look inside refs and detect if let &None = ... Fixes rust-lang/rust-clippy#5396 changelog: redundant_pattern_matching: look inside Refs to fix FNs with "if let &None = .. "
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
Labels
E-needs-test
Call for participation: An issue has been fixed and does not reproduce, but no test has been added.
I-ICE
Issue: The compiler panicked, giving an Internal Compilation Error (ICE) ❄️
After #6990 lands the following fails with an error message. (It currently ICEs.)
I'm not sure whether this is correctly not-constant, or whether it should compile fine. In the former case, is this something that should be handled in
check_const.rs
rather thanconst_eval.rs
(where it is handled currently (0d0c004))?That testcase requires the
match
with they
.(This is filed because I wasn't sure about whether this is a valid testcase for #6990 or whether it shouldn't be triggering this code path at all.)
The text was updated successfully, but these errors were encountered: