⚡️ Speed up function get_ref
by 10% in pydantic/_internal/_core_utils.py
#38
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.
📄
get_ref()
inpydantic/_internal/_core_utils.py
📈 Performance improved by
10%
(0.10x
faster)⏱️ Runtime went down from
26.7 microseconds
to24.2 microseconds
(best of316
runs)Explanation and details
Here is a more optimized version of the given program by removing the unnecessary
None
as the default value fors.get('ref')
, because theget
method already returnsNone
if the key does not exist.This maintains the functionality and type hinting, while being slightly more concise and efficient in terms of performance.
Correctness verification
The new optimized code was tested for correctness. The results are listed below.
🔘 (none found) − ⚙️ Existing Unit Tests
✅ 39 Passed − 🌀 Generated Regression Tests
(click to show generated tests)
🔘 (none found) − ⏪ Replay Tests