Perf: Optimize string concatenation in parse_uncertainty #112
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.
This pull request optimizes string construction in
parse_uncertaintyby replacing+concatenation with.join().The Issue: In Python, strings are immutable. Using
+to combine multiple string segments forces the interpreter to create a new string object and copy the content for every concatenation step. This results in inefficient memory usage and unnecessary overhead, particularly when constructing strings from multiple parts.The Solution: I refactored the string construction logic to use
''.join(). This approach ensures linear time complexityO(n)because the total size of the final string is calculated once, and memory is allocated efficiently.This is in line with standard python performance recommendation: https://peps.python.org/pep-0008/#programming-recommendations