[Performance] Make determining rune width faster #1722
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.
Similar to #1719, rune width lookups also make up a significant share of Micro's CPU consumption. The go-runewidth package allows for a fast path optimization in the same vein as the previous PR, and this PR switches to my fork of go-runewidth that implements this optimization. I intend to upstream this change, assuming the maintainer is interested.
This provides another substantial speedup for buffer operations: