perf(source-map): add value source offset index - #122
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
MarkdownSourceMap.getValueSourceIndex().MarkdownValueSourceIndextype.Benchmark
The benchmark used Node 24.15.0.
It used 10,000 newline candidates and 50,000 queries per sample.
It ran 12 alternating A/B samples in one process.
getSourceRange(node, index, index)sourceOffsetAt(index)The median time decreased by 76.0%.
The source index was 4.17 times faster.
This benchmark measures boundary lookup only.
It does not claim a full lint runtime improvement.
Tests
pnpm run buildpnpm run lintpnpm testSecurity
No sensitive data is included.
No redaction was required.
Closes #121.