-
Notifications
You must be signed in to change notification settings - Fork 13.3k
[MIR] span_mirbug! should be an error #35499
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
Not before we’re absolutely sure there’s really no more warnings produced by this. |
@nagisa We can check crater after turning them into ICEs. |
@nagisa I'm not 100% sure I understand that logic -- since we're in orbit now, and MIR is really being used, it seems to me that broken MIR has to stop compilation. For example see #35883 (comment) -- crash in safe code caused by generating a binary from bad MIR (indicating a bug in typeck). |
Can someone give an update here? Should we change mirbug to ICE? It seems reasonable... |
This is already done. |
IIUC, span_mirbug! was an warning while MIR was in development. It's time to make span_mirbug! an error. (Or if it's really supposed to be a warning, rename the macro)
https://github.com/rust-lang/rust/blob/master/src/librustc_mir/transform/type_check.rs#L29-L36
The text was updated successfully, but these errors were encountered: