{{ message }}
bpo-35582: Inline arguments tuple unpacking in handwritten code.#11524
Merged
serhiy-storchaka merged 3 commits intoJan 12, 2019
Merged
Conversation
Member
Sorry, something went wrong.
Inline PyArg_UnpackTuple() and _PyArg_UnpackStack() in performance critical code in the builtins and operator modules.
Member
Author
|
This PR rewrites again some of code changed in #11435. It looks now simpler but has the same performance. |
Sorry, something went wrong.
vstinner
reviewed
Jan 11, 2019
vstinner
approved these changes
Jan 11, 2019
vstinner
left a comment
vstinner
left a comment
Member
There was a problem hiding this comment.
LGTM but please keep "w" variable in builtin_iter() as I proposed in a comment.
Sorry, something went wrong.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Reviewers
4 participants
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.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.
Inline PyArg_UnpackTuple() and _PyArg_UnpackStack() in performance
critical code in the builtins and operator modules.
https://bugs.python.org/issue35582