Avoid double traversal when restoring CR diff lines - #15885
Merged
josevalim merged 1 commit intoSep 11, 2026
Conversation
Assisted-by: Codex:GPT-6 Signed-off-by: Clayton Gentry <clayton@podstock.io>
claytongentry
force-pushed
the
optimize-cr-diff-reversal
branch
from
September 11, 2026 12:23
605531e to
05ecf3e
Compare
Member
|
💚 💙 💜 💛 ❤️ |
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.
Assisted-by: Codex:GPT-6
Replace Enum.reverse/1 followed by Enum.concat/2 with Enum.reverse/2 in the CR diff handling base cases, avoiding an extra traversal and copy of the reversed list.
Benchmark is noisy for small input timings and shows no or negligible improvement, but shows reduced average execution time by ~8% at 100 lines and ~11-12% at 1000 lines. 1000 line case also shows ~5% less memory and ~5% fewer reductions.
Bench:
Results