Skip to content

[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

Closed
scottcarr opened this issue Aug 8, 2016 · 5 comments
Closed

[MIR] span_mirbug! should be an error #35499

scottcarr opened this issue Aug 8, 2016 · 5 comments

Comments

@scottcarr
Copy link
Contributor

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

@nagisa
Copy link
Member

nagisa commented Aug 8, 2016

Not before we’re absolutely sure there’s really no more warnings produced by this.

@eddyb
Copy link
Member

eddyb commented Aug 22, 2016

@nagisa We can check crater after turning them into ICEs.

@durka
Copy link
Contributor

durka commented Aug 22, 2016

@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).

@Mark-Simulacrum
Copy link
Member

Can someone give an update here? Should we change mirbug to ICE? It seems reasonable...

@arielb1
Copy link
Contributor

arielb1 commented May 12, 2017

This is already done.

@arielb1 arielb1 closed this as completed May 12, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants