⚡️ Speed up method StringSplitter._normalize_f_string
by 202% in src/black/trans.py
#59
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.
📄
StringSplitter._normalize_f_string
insrc/black/trans.py
✨ Performance Summary:
202%
(2.02x
faster)16.0 microseconds
down to5.29 microseconds
(best of63
runs)📝 Explanation and details
Certainly! Here's a more optimal version of the provided code.
Optimizations.
assert_is_leaf_string
:fstring_contains_expr
:{
and}
which is often enough for detection._normalize_f_string
:str.replace
for double brace normalization which is generally faster thanre.sub
.These improvements make the function more efficient while preserving the original behavior.
✅ Correctness verification
The new optimized code was tested for correctness. The results are listed below:
📣 **Feedback**
If you have any feedback or need assistance, feel free to join our Discord community: