-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Rewrite doc_markdown
to use pulldown-cmark
#1799
Conversation
doc_markdown
to use pulldown-cmark
doc_markdown
to use pulldown-cmark
This is ready to be merged. |
Appveyor build looks to have failed because of caching problem. |
The windows build is failing because of
Any idea what is going on? |
Rustc is distributing its own pulldown... somehow we're getting a conflict with the distributed one. Do we set any unusual path env var values in appveyor? |
Looks like we do. Cc @llogiq, I've no idea how either Appveyor or Windows work. |
05377ff
to
953be0f
Compare
This works \o/ |
No, but I would like a quick performance comparison. |
You can remove my two commits then. Seems they had no effect and were messy to begin with |
Before:
After:
Does not look like there is much of a difference. Any idea of a biggish crate with a lot of docs? |
(feel free to merge, fwiw) |
I hope this will fix most false positives, and maybe some true negatives, and won't introduce too much new FP.
Use the one from `rustc`'s, which avoids "multiple matching crate" errors.
Rewrite
doc_markdown
to usepulldown-cmark
.This should fix a number of false positives and true negatives. It should mean that the lint can be extended more easily in the futur.
WIP: I have not got the spans quite right yet. The best I can do is line-wise (actually attribute-wise) spans, while the current lint report the actual problematic word.Fix #1469.