-
Notifications
You must be signed in to change notification settings - Fork 13.3k
Follow up to #51508, make parse_block public instead parse_block_expr #51549
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
r? @pnkfelix (rust_highfive has picked a reviewer for you, use r? to override) |
@bors r+ |
📌 Commit 8096b31 has been approved by |
⌛ Testing commit 8096b31720e487d79d8dbef557a53ab055861a38 with merge 2bef91921e2146de30eb27cc1db20d893979b7ae... |
💔 Test failed - status-appveyor |
@bors retry
🤔 |
⌛ Testing commit 8096b31720e487d79d8dbef557a53ab055861a38 with merge 7684f4a1d9c6a22bcdb98b03ce6b7794dbd8163d... |
💔 Test failed - status-appveyor |
@bors retry rollup |
⌛ Testing commit 8096b31720e487d79d8dbef557a53ab055861a38 with merge 76330b23c66689fb06dfb8099be1a72198070be0... |
💔 Test failed - status-appveyor |
…lock_expr This is an follow up to rust-lang#51508 I mistakenly made parse_block_expr public instead of parse_block. This fixes this.
Rebased, tests were broken on nightly. |
@bors retry |
@bors r+ |
📌 Commit b1c0857 has been approved by |
☀️ Test successful - status-appveyor, status-travis |
This is an follow up to #51508
I mistakenly made parse_block_expr public instead of parse_block.
This fixes this.