⚡️ Speed up Span.move()
by 24% in rich/text.py
#7
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.
📄
Span.move()
inrich/text.py
📈 Performance improved by
24%
(0.24x
faster)⏱️ Runtime went down from
45.1 microseconds
to36.3 microseconds
Explanation and details
Certainly! To improve the performance of the given code, we need to focus on avoiding redundant operations and simplifying the logic where possible while maintaining the functionality intact. Here's the optimized version.
Note: The
Span
class was previously defined twice in your code, which is redundant and incorrect. I've consolidated the class definition accordingly.Optimizations Made.
Span
class declaration.split
andright_crop
to reduce the number of comparisons and ensure early exits when applicable.By reducing redundancy and enhancing the conditional checks' efficiency, the updated code should generally perform better while maintaining the original functionality.
Correctness verification
The new optimized code was tested for correctness. The results are listed below.
✅ 106 Passed − ⚙️ Existing Unit Tests
(click to show existing tests)
✅ 13 Passed − 🌀 Generated Regression Tests
(click to show generated tests)
🔘 (none found) − ⏪ Replay Tests