-
Notifications
You must be signed in to change notification settings - Fork 13.2k
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
Make span_fatal and parse_block public #51508
Conversation
span_fatal and parse_block were made private in rust-lang#51265. These methods are used in stainless. Related rust-lang#51498 rust-lang#51504
Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @michaelwoerister (or someone else) soon. If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes. Please see the contribution instructions for more information. |
@bors r+ rollup |
📌 Commit 6fd9ede has been approved by |
☀️ Test successful - status-appveyor, status-travis |
…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.
span_fatal and parse_block were made private in #51265. These methods are used in stainless.
Related #51498 #51504