⚡ Faster SequenceSet#normalize when frozen#556
Merged
Uh oh!
There was an error while loading. Please reload this page.
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.
Calling
SequenceSet#normalizeon a frozen set can be more than 4x faster, by simply re-parsing@stringand scanning its elements, rather than fully generating a new string and comparing it with@string.Please note that these results vary significantly based on benchmark settings (e.g: size of the sequence set) and randomized factors (e.g: how early in the string is the first out-of-order or abnormal string).
Also, I manually adjusted the benchmark in order to compare prior unreleased commits in this branch vs this PR, because #554also provides a significant performance boost. So "generate and compare" includes #554, and "reparse and check" represents this PR.