-
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
upgrade rustdoc's pulldown-cmark to 0.4.1 #60140
Conversation
(rust_highfive has picked a reviewer for you, use r? to override) |
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 |
Thanks for doing it! Please ping me once CI passed so I can re-review it (but currently looks good). |
@GuillaumeGomez Travis is green! |
diag.span_warn(DUMMY_SP, &err.to_string()); | ||
} | ||
|
||
find_testable_code(&input_str, &mut collector, codes); |
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.
Why those changes?
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.
While I was making the changes to find_testable_code
, I noticed that the error case isn't actually possible. The code attempts to handle a missing codeblock end event but I don't think pulldown-cmark
can actually emit that sequence of events. Furthermore, there isn't a test case in the compiler that emits the error message.
So, I removed the error case, changed the signature from Result
to ()
, and updated all the call-sites to remove the error emitting code.
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.
I see, good catch then!
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.
"Documentation test in private item"); | ||
diag.emit(); | ||
} | ||
find_testable_code(&dox, &mut tests, ErrorCodes::No); |
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.
Same question.
self.sess.diagnostic().span_warn(attrs.span.unwrap_or(DUMMY_SP), | ||
&err.to_string()); | ||
} | ||
markdown::find_testable_code(&doc, self.collector, self.codes); |
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.
Same question.
@bors: r+ |
📌 Commit 2f59cf6438e65443dc94dbe3b0beec9903948e3b has been approved by |
🔒 Merge conflict This pull request and the master branch diverged in a way that cannot be automatically merged. Please rebase on top of the latest master branch, and let the reviewer approve again. How do I rebase?Assuming
You may also read Git Rebasing to Resolve Conflicts by Drew Blessing for a short tutorial. Please avoid the "Resolve conflicts" button on GitHub. It uses Sometimes step 4 will complete without asking for resolution. This is usually due to difference between how Error message
|
Rebased. |
@bors: r+ |
📌 Commit 3030164 has been approved by |
upgrade rustdoc's pulldown-cmark to 0.4.1 Fixes #59194.
☀️ Test successful - checks-travis, status-appveyor |
Fixes #59194.