perf: Optimize iterator advance() call #4237
Merged
Conversation
This file contains 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
Skylion007
changed the title
rwgk
approved these changes
Oct 12, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
Inspired by #4232, I found one other place where we ignore the return value of C-API function and blindly call PyErr_Occurred(). Worse, it's in a very hot piece of code, (the advance() function for iterators in C++ bindings). The official C-API documentation example code clearly shows that PyErr_Occurred() check is only necessary when the iteration terminates (ie. the next pointer returned is not null).
PyErrOccurred()involves a good deal of pointer chasing so best to avoid having to so every step: https://github.com/vstinner/pythondev/blob/d7a8d069e5a5d7ad26503f98a2d29c1508a03e73/assembly.rstSuggested changelog entry: