-
-
Notifications
You must be signed in to change notification settings - Fork 30.9k
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
Merge BINARY_SUBSCR_LIST_INT with BINARY_SUBSCR_LIST_TUPLE #91407
Comments
The implementations of BINARY_SUBSCR_LIST_INT and BINARY_SUBSCR_TUPLE_INT are almost identical. They can be merged, so there is one opcode less and the code is shared. |
The code is very similar, but they deal with different underlying objects, so one calls
Line 2105 in 98ff4a6
Line 129 in 2bde682
Also, there's a typo in the issue title, it should be |
@kevin-chau @markshannon Thanks for the feedback on the PR. Merging the two opcodes does not seem a good idea at this moment. Factoring out common code is possible (see item 4. below), but I would like to know whether this is worth the effort.
The
I doubt this is common in real code.
with
(several other variations have been tried as well). This showed no performance improvements
Is the factoring out worthwhile to make a new PR for? Performance benchmarks for 4.Microbenchmark
results in Pyperformance
|
@markshannon The issue can be closed afaik. I am not allowed (maybe because it was opened by the mannequin?) |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: