Optimize _camelcase_to_underscore (and thus String.capitalize)
#100016
+16
−8
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
…ng a rolling cache of character attributes, instead of re-computing each iteration.
Mickeon
changed the title
_camelcase_to_underscore (and thus String.capitalize)
clayjohn
reviewed
Dec 5, 2024
clayjohn
approved these changes
Dec 5, 2024
|
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.
…by using a rolling cache of character attributes, instead of re-computing each iteration.
There's definitely some more optimization that could be done here, but this is low hanging fruit.
New implementation leads to e.g. 1.2x speed improvement for
to_camel_case.