Precompile Markdown parsing AND printing#55752
Conversation
|
[This shouldn't need a full CI, since a trivial tested add-on.] This is likely the better backport target for 1.11, assuming it only adds to pkgimage (i.e. not the sysimage), not concerned about bloating it, a bit. This could precompile a bit more for stdout, not just stderr, but unsure how to do that, also likely not a large improvement. It also misses some tags, for images, not as important, maybe easy to add, but I don't want this to hold up releasing 1.11. Can always be added later... |
|
Julia support the CommonMark extension: https://www.markdownguide.org/extended-syntax/ but is it the only one, e.g. no R Markdown allowed? The parser will not fail at any extension, just ignore it, so might be ok to include here, for later compatibility? I was looking into what basic tags to add here, and what more, maybe, I see we likely do not support latest 2024 CommonMark https://spec.commonmark.org/0.31.2/changes.html since I found in the code: https://spec.commonmark.org/0.19/#absolute-uri |
|
Note that this will precompile many things for which is not the type that will typically be used when printing things. |
|
This is now done. You can't simply skip devnull, because then it would show, and I'm not sure how to avoid that differently, than I do now. |
|
I think this is now done for the 1.11 backports. Only question is the precompile I got for Markdown (probably harmless to have here; or skip it): precompile(Tuple{typeof(Base.:(^)), String, Int64}) |
|
Bump. This was ok for me locally, the CI failure is most likely unrelated, and this can and should be merged, and ideally go into 1.11, since a small better change and this line seems not to be about me: Line 100 in 7a76e32 |
|
Bump. False alarm CI is a problem for PRs getting accepted I think (a bit too common IMHO, then I miss out on some real CI failures): |
|
This can be merged as is. I'm trying a rebase though (for the first time), I think that's the solution to CI false alarms. I meant to do rebase, after button seemed not responding, think I chose the option above, "to branch"(?) by accident, not even sure what it does or if I made worse... |
|
Any timings before/after? |
|
E.g.: |
628169b to
470f78e
Compare
|
Ok, and those 0.1 seconds are annoying/noticable when? |
|
This doesn't affect the sysimage size, so I think precompilng as much as possible ok here? I had already fixed the major issue I had with |
…ME to actually render the markdown
--------- Co-authored-by: Kristoffer <kcarlsson89@gmail.com> Co-authored-by: Ian Butterworth <i.r.butterworth@gmail.com> (cherry picked from commit 0dd78f7)
Improvement on top of #55715, replacing it, to also precompile printing. And then also fixing parsing and using regression for #55706.