-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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 pulldown cmark #2401
base: master
Are you sure you want to change the base?
Upgrade pulldown cmark #2401
Conversation
Needs rust-lang/mdBook#2401 to land before it can be landed, because mdbook requires pulldown-cmark 0.10, so there is a type mismatch on `Event`: ``` error[E0271]: expected `Parser<'_>` to be an iterator that yields `Event<'_>`, but it yields `Event<'_>` --> src/lib.rs:372:39 | 372 | html::push_html(&mut buf, events); | --------------- ^^^^^^ expected `Event<'_>`, found `pulldown_cmark::Event<'_>` | | | required by a bound introduced by this call | = note: `pulldown_cmark::Event<'_>` and `Event<'_>` have similar names, but are actually distinct types note: `pulldown_cmark::Event<'_>` is defined in crate `pulldown_cmark` --> /Users/chris/.cargo/registry/src/index.crates.io-6f17d22bba15001f/pulldown-cmark-0.10.3/src/lib.rs:354:1 | 354 | pub enum Event<'a> { | ^^^^^^^^^^^^^^^^^^ note: `Event<'_>` is defined in crate `pulldown_cmark` --> /Users/chris/.cargo/registry/src/index.crates.io-6f17d22bba15001f/pulldown-cmark-0.11.0/src/lib.rs:366:1 | 366 | pub enum Event<'a> { | ^^^^^^^^^^^^^^^^^^ = note: perhaps two different versions of crate `pulldown_cmark` are being used? ```
Sorry for the ping @ehuss, but from a glance at latest commits it seem you're in charge of PRs.
|
As the comment says, we can't update it at this time. See #2387. We will likely update this when we do a 0.5 release. |
Hi and thanks for this beautiful piece of tooling, I simply love it since the first time I discovered it!
I updated
pulldown-cmark
but noticed the comment saying not to inCargo.toml
, so feel free to dismiss this PR if this is not supposed to happen from an external contribution.If however you do accept this PR, I'd like to add a mathematical expression to the tests for the sake of completeness but I'd appreciate that you point me which markdown is the most appropriate, so putting this under draft for now.
Thanks!