-
Notifications
You must be signed in to change notification settings - Fork 13k
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
[breaking-batch] Move more uses of panictry!
out of libsyntax
#31631
Conversation
r? @sfackler (rust_highfive has picked a reviewer for you, use r? to override) |
...I messed that up. Fixing! |
r? @nrc |
This should work. I'm not too happy about |
☔ The latest upstream changes (presumably #31530) made this pull request unmergeable. Please resolve the merge conflicts. |
[breaking-change] for syntax extensions
Rebased |
@@ -86,7 +84,7 @@ pub fn compile_input(sess: &Session, | |||
// possible to keep the peak memory usage low | |||
let (outputs, trans) = { | |||
let (outputs, expanded_crate, id) = { | |||
let krate = phase_1_parse_input(sess, cfg, input); | |||
let krate = panictry!(phase_1_parse_input(sess, cfg, input)); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we shouldn't panic here, we should return an error instead
r+ with the above changes (sorry the review took so long). |
@bors: r+ |
📌 Commit 11e0ba4 has been approved by |
[breaking-batch] Move more uses of `panictry!` out of libsyntax
Ah, dang it, I totally forgot about #31645, now this'll break stuff |
No description provided.