Optimize Kramdown::JekyllDocument#to_html
calls
#8041
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
By having
:to_html
explicitly defined for theKramdown::JekyllDocument
instances, the benefits are following::to_html
to"to_html"
."html"
from the method name and consequent conversion into"Html"
.require "kramdown/converter/html"
and consequent constant-lookup.The optimization is to bypass steps above and call
Kramdown::Converter::Html.convert
directly. This is possible becauseKramdown::Converter::Html
is set up to be autoloaded if not available already.Context
Prior, I made an attempt to propose this patch at the upstream kramdown core : gettalong/kramdown#644. It got rejected since the change brought little value to the kramdown project.
However, the patch could have relatively more value to Jekyll because:
:to_html
method in its conversion process.markdownify
Liquid filter which under-the-hood uses the same API.The upstream code as of
kramdown-2.1.0
is: