-
-
Notifications
You must be signed in to change notification settings - Fork 35k
bpo-31179: Make dict.copy() up to 5.5 times faster. #3067
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
6140e4c
60ed4ad
03d51ac
bb6d328
47413f6
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1 @@ | ||
| Make dict.copy() up to 5.5 times faster. | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. The one case it slowed down was an empty dict ... is it worth a special path to drop out and just create a new empty dict then?
Member
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Added a fast-path for empty dicts. |
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are these test changes actually related to the code changes? Or are they just test hardening that you thought of because of the new code? If so, the test improvements should go in regardless of whether or not the code changes do, and ideally as a separate commit.