-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
Avoid StringReader when checking code blocks for syntax errors #76068
Conversation
This fails the r? @GuillaumeGomez (but this a WIP due to the test failure) |
Yes: specifying r? @username directly in the PR description leads to ping amplification (as PR description is included in the commit message generated by bors). So I write ghost and then assign the actual reviewer in the second comment. |
Ah, I got confused for a moment. I forgot this is rustdoc and @GuillaumeGomez is a reviewer, I thought you made a typo on the reviewer. |
1404c72
to
d1a3e99
Compare
Fixed the test failure, should be ready to review now! |
Looks good to me. Since you ping @petrochenkov, I'll let them take a look first as well. cc @jyn514 |
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.
LGTM, I don't know this part of the code very well but if @matklad says parse_stream_from_source_str
is more stable I trust his judgement.
`parse_stream_from_source_str` is a more stable API to convert a string into a bunch of tokens, and it also catches errors about mismatched parenthesis.
d1a3e99
to
1baf3ff
Compare
parse_stream_from_source_str
is a more stable API to convert astring into a bunch of tokens, and it also catches errors about
mismatched parenthesis.
r? @ghost