-
Notifications
You must be signed in to change notification settings - Fork 13.3k
Exhaustively match on {Statement,Terminator}Kind
during const checking
#71336
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
Conversation
The job Click to expand the log.
I'm a bot! I can only do what humans tell me to, so if this was not helpful or you have suggestions for improvements, please ping or otherwise contact |
1b4beb9
to
fb33815
Compare
The job Click to expand the log.
I'm a bot! I can only do what humans tell me to, so if this was not helpful or you have suggestions for improvements, please ping or otherwise contact |
fb33815
to
7954339
Compare
@oli-obk seems like CI is passing with the proper spans now. |
@bors r+ Thanks, those diagnostics are much better! |
📌 Commit 152c065 has been approved by |
Rollup of 4 pull requests Successful merges: - rust-lang#71280 (Miri: mplace_access_checked: offer option to force different alignment on place) - rust-lang#71336 (Exhaustively match on `{Statement,Terminator}Kind` during const checking) - rust-lang#71370 (Added detailed error code explanation for issue E0696 in Rust compiler.) - rust-lang#71401 (visit_place_base is just visit_local) Failed merges: r? @ghost
This adds a pre-monomorphization error for inline assembly in a const context as well.
r? @oli-obk