optimization: speed up Parser#siblingsCorrection #1494
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.
Part of #1049
What is the purpose of this PR?
Description
This PR optimizes
Parser#siblingsCorrection
in two ways:.findLast
in.siblingsCorrection
with O(1) lookupsC
in the below chartsortNumber
is also optimized.sC + sN
in the below chartTest data: 1500+ options as mentioned in #1049
As the result, the entire process time on many
<option>
s is 6.5% shorter compared to v4.1.1.(4.16 / 4.45 = 0.935)
Checklist
Fill out the checks for the applicable purpose.
@markuplint/config-presets