You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So vectorcall protocol allows more efficient calling without needing to construct Python containers.
Still, it needs a tuple for knames.
I am modifying keyword arguments (functools.partial), where I sometimes need to modify kwnames and this results in big performance penalty when this is the case.
Not sure if this could result in more general performance improvement by not having to construct tuple in other places, but maybe this would be worthwhile considering?
So
vectorcall
protocol allows more efficient calling without needing to construct Python containers.Still, it needs a
tuple
forknames
.I am modifying keyword arguments (
functools.partial
), where I sometimes need to modifykwnames
and this results in big performance penalty when this is the case.Not sure if this could result in more general performance improvement by not having to construct
tuple
in other places, but maybe this would be worthwhile considering?E.g.
Or something similar.
Will look into this in due time, but thought maybe it is worth posting to get some thoughts.
The text was updated successfully, but these errors were encountered: