[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 |
| 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.
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.