-
Notifications
You must be signed in to change notification settings - Fork 12.7k
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
Prevent MIRI ICE by bubbling up #100967
Prevent MIRI ICE by bubbling up #100967
Conversation
This comment has been minimized.
This comment has been minimized.
⌛ Trying commit 8b0690a with merge 4ef10657f99de0ed2da88f2ce0114812b9927fbf... |
Only the new one, I would like to fix debug assertion one too but I don't know where to even begin with that. |
Fair.^^ |
If we end up landing this, I can put up a fix to change the debug assertion in a way that's not as risky as just removing it. I'm gonna continue to see if we can revert the underlying root cause (the fact we currently don't normalize opaques with escaping bound vars). |
☀️ Try build successful - checks-actions |
do you want to keep trying or should we merge this PR now and you can work on a revert of it? |
Well, a debug assertion that can actually be triggered is always a bug, and makes me worried about which things might break in later parts of the compiler due to the invariant violation. So it should probable at least become a regular assertion to ensure correct execution. And then it's still an ICE, which is a bug -- but it needs a nightly feature to be triggered. I also assume if it can be triggered in Miri there is some way to trigger it with rustc, though I don't know how. I don't know of any real-life code that runs into this, though. |
Superseded by #100980 I think |
This fixes MIRI ICE which resulted from this work.
r? @oli-obk