Trimmer optimization#56
Merged
Merged
Conversation
Owner
|
Nice! I'll test that as soon as I can. |
bleroy
reviewed
Apr 1, 2026
bleroy
reviewed
Apr 1, 2026
bleroy
requested changes
Apr 1, 2026
Owner
bleroy
left a comment
There was a problem hiding this comment.
Thanks for the contribution, this looks mostly good, I just have a few minor requests.
Owner
|
Thanks! |
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.
Current trimmer implementation use Regex which is slow.
Replace it with native string manipulation.
This is about 100x faster and also this don't reallocate a string if not needed, so less allocation on average.
Before :
After :