-
Notifications
You must be signed in to change notification settings - Fork 13.3k
Recursive type with infinite size leads to internal compiler error (try_mark_green() - Forcing the DepNode should have set its color) #57373
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
Comments
I'm unable to reproduce this on Linux using this command line
This might be caused by a previous incremental compilation. |
I just ran into this issue myself. I changed an enum to be recursive (a bug on my part) and the compiler panicked. After running Looks like @jonas-schievink is correct in blaming previous incremental compilation. Here is my full error output from before running
|
triage: P-high. |
assigning to @nikomatsakis with expectation that they will delegate. |
triage: reassigning to self (for either investigation or delegation). |
triage: downgrading to P-medium because having this in weekly triage does not make sense. |
I just ran into this ICE. As @z2oh pointed out after |
Can probably be closed as a duplicate of #61323? |
Seems plausible. Thanks! |
A (rather complex) enum-based data structure (code below) lead to the following compiler panic:
Instead, I would have expected the following error message:
This is the code:
Important Note: For submitting this bug report, I tried to sanitize the data structure (less variants, simplified names, etc.), however doing any changes (even if just renaming
Action
to something likeOuter
) removed the bug and resulted in the "infinite size" error, as expected.The text was updated successfully, but these errors were encountered: