-
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
buffer lexer errors in rustdoc syntax checking #67563
Conversation
1a52ae5
to
ac14d81
Compare
The job Click to expand the log.
I'm a bot! I can only do what humans tell me to, so if this was not helpful or you have suggestions for improvements, please ping or otherwise contact |
ac14d81
to
bfa1929
Compare
It's a bit better, however we lost the context. It now just says "we have this error in this code block" but doesn't provide the line or anything. Can you provide more information for the users? |
We could provide the line/col number, but doing anything more would be significant work that I would rather explore in a separate PR (I'm not sure that we can translate the spans in the general case). To be clear, this is fixing a regression (we've reopened #53919) and bringing the output back to where it was in 1.34.0. |
Then please add a TODO in the code and open an issue so we don't lose track of this. Then r=me. Thanks a lot! |
bfa1929
to
544032c
Compare
@GuillaumeGomez Added a TODO and created the issue. |
The job Click to expand the log.
I'm a bot! I can only do what humans tell me to, so if this was not helpful or you have suggestions for improvements, please ping or otherwise contact |
☔ The latest upstream changes (presumably #67853) made this pull request unmergeable. Please resolve the merge conflicts. |
544032c
to
0b79474
Compare
0b79474
to
1ad928e
Compare
Rebased. |
@bors: r+ |
📌 Commit 1ad928e has been approved by |
buffer lexer errors in rustdoc syntax checking The code isn't ideal (I really would like to display the errors inline), but this at least gets us to where we were before #63017.
☀️ Test successful - checks-azure |
The code isn't ideal (I really would like to display the errors inline), but this at least gets us to where we were before #63017.