-
Notifications
You must be signed in to change notification settings - Fork 13.1k
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
Use proper span for break and continue labels #28170
Conversation
13f6302
to
3c6e421
Compare
@bors: r+ d4921874db5cf5f4e3d2fdd3035926beaa0aa2f8 |
d492187
to
93a1cbc
Compare
Needs re-r+. |
@bors: r+ 93a1cbc91ad340b9586740add923832362388b9f |
🔒 Merge conflict |
93a1cbc
to
1a69348
Compare
rebased |
⌛ Testing commit c493084 with merge 3575f06... |
⛄ The build was interrupted to prioritize another pull request. |
⌛ Testing commit c493084 with merge e5c5046... |
⛄ The build was interrupted to prioritize another pull request. |
@bors r- This fails parse tests |
The error:
The test itself seems to expect errors exactly as emitted. I’m baffled. Are 32bit linux builders broken? |
Could be, not sure. check-stage1 passes fine for me without your PR, so it's either an intermittent, brokenness in the PR, or brokenness introduces in confluence in another PR. I can't see how this PR could break parsing, though. I'll poke further once I'm sure that the rollup passes check-stage2 locally |
@bors p=1 |
r? @alexcrichton