-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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
Update pulldown-cmark version to 0.9 #92252
Conversation
I opened pull requests for clippy and mdbook as well. |
927f9ba
to
83c25a4
Compare
As asked in the clippy PR, I updated their code in here directly. |
The Clippy changes look good to me, thank you for the update! 👍 Could you separate the clippy changes into an extra commit? That helps with syncing it back (I forgot to me mention that earlier 😅) |
83c25a4
to
4e2024c
Compare
@xFrednet I did it originally and for some reason I thought it might be simpler to merge both commits. Well, it's in its own commit now. :) |
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.
Thank you! The Clippy changes look good to me. I leave the other changes and the r+ to @camelid since this PR also includes changes in rust 🙃
@camelid Do you mind for us to merge this PR until mdBook has a new release? I'll send another PR at this moment. |
@bors r=camelid,xFrednet |
📌 Commit 4e2024c has been approved by |
@bors rollup=never (pulldown's perf may have changed) |
⌛ Testing commit 4e2024c with merge e41f6c3d619f5443c1095a14784edebfccc56abe... |
The job Click to see the possible cause of the failure (guessed by this bot)
|
💔 Test failed - checks-actions |
☀️ Test successful - checks-actions |
Finished benchmarking commit (8ed935e): comparison url. Summary: This benchmark run did not return any relevant changes. If you disagree with this performance assessment, please file an issue in rust-lang/rustc-perf. @rustbot label: -perf-regression |
Hmm, this PR led to a lot of small perf regressions on doc benchmarks. There were no improvements, and serde in particular regressed by 0.34%, which is considered above the significance threshold. @rustbot label: +perf-regression |
…elid,xFrednet Update pulldown-cmark version to 0.9 Fixes rust-lang#92206. r? `@camelid`
cc @marcusklaas – just FYI about the perf regressions that seem to have occurred between 0.8.0 and 0.9.0 of pulldown-cmark: #92252 (comment) |
What options does rustdoc use? We did add a new feature (heading attributes), that may add a little bit of complexity for heading parsing. But I will investigate the slowdown myself also. Thanks for the heads-up! |
I think these are all the features we use: /// Options for rendering Markdown in the main body of documentation.
pub(crate) fn main_body_opts() -> Options {
Options::ENABLE_TABLES
| Options::ENABLE_FOOTNOTES
| Options::ENABLE_STRIKETHROUGH
| Options::ENABLE_TASKLISTS
| Options::ENABLE_SMART_PUNCTUATION
} Thanks for looking into it! ❤️ |
Fixes #92206.
r? @camelid