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
Use vectorcall by default #5804
Merged
Merged
Changes from all commits
Commits
Show all changes
17 commits
Select commit
Hold shift + click to select a range
513bf17
(WIP) use vectorcall by default
da-woods e410722
Apply to "int.from_bytes"
da-woods 7464ed7
Detach decision to use vectorcall from unpack methods
da-woods 2295117
Small fixes
da-woods b5bf080
Add gotref and string check
da-woods ad07727
Merge remote-tracking branch 'real_origin/master' into vectorcall-eve…
da-woods 7d67334
Avoid some unnecessary checks
da-woods 0d83a70
Add a no-copy shortcut to merged dict node
da-woods eec7bfe
Fix simplecallnode optimization
da-woods 38e701c
Use old name appropriately
da-woods 1f37586
Fix self-build
da-woods f80394e
Move function_type
da-woods 050036f
Merge branch 'master' into vectorcall-everywhere
scoder 4c5ea02
Comments from review
da-woods 955886c
Add tests
da-woods 0dde3c9
Comments from review
da-woods 5df97d0
Replace two more occurrences of self.kwargs.key_value_pairs
scoder File filter
Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
There are no files selected for viewing
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
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
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.
It seems that the two
can_be_…
functions are always called before callingfrom_node()
. That seems redundant. Why not let aPyMethodCallNode
classmethod try to optimise the call (thus, maybetry_to_optimise_call()
), and if it can't, return the original node unchanged?Feel free to add a
if node is (not) replacement
short-cut to thereplace()
method to simplify this further.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.
I'm disagreeing with this for now.
There's a good chunk of duplication between
SimpleCallNode
andGeneralCallNode
, but there there's also significant differences (aCloneNode
check, the name of the attribute used for the positional arguments, handling of keyword arguments).So I think the logic need to be duplicated either way, either here or with an
isinstance
check inPyMethodCallNode
. I think it's slightly better here (where the visitor has found the classes for us).I don't have a hugely strong opinion - it just doesn't look like a significant improvement to me.