-
-
Notifications
You must be signed in to change notification settings - Fork 14.9k
Error on constant pointer dereference #6991
Copy link
Copy link
Closed
Labels
E-needs-testCall for participation: An issue has been fixed and does not reproduce, but no test has been added.Call for participation: An issue has been fixed and does not reproduce, but no test has been added.I-ICEIssue: The compiler panicked, giving an Internal Compilation Error (ICE) ❄️Issue: The compiler panicked, giving an Internal Compilation Error (ICE) ❄️
Metadata
Metadata
Assignees
Labels
E-needs-testCall for participation: An issue has been fixed and does not reproduce, but no test has been added.Call for participation: An issue has been fixed and does not reproduce, but no test has been added.I-ICEIssue: The compiler panicked, giving an Internal Compilation Error (ICE) ❄️Issue: The compiler panicked, giving an Internal Compilation Error (ICE) ❄️
Type
Fields
Give feedbackNo fields configured for issues without a type.
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.rsrather thanconst_eval.rs(where it is handled currently (0d0c004))?That testcase requires the
matchwith 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.)