Improve performance of word motions #3662
Merged
Conversation
This file contains 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
|
🍾 thanks! |
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.
What this PR does / why we need it
This PR fixes the performance issue reported in #3660. It changes the definition of the following properties in
Position:_nonWordCharRegex_nonBigWordCharRegex_nonCamelCaseWordCharRegex_sentenceEndRegex_nonFileNameRegexso that the construction of these regular expressions is performed only once.
The time to complete the benchmark task proposed in #3660 was 431ms in average, which is 12x faster than the current version on my machine.
Which issue(s) this PR fixes
fixes #3660.
Special notes for your reviewer: