-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Removed last usages of scalar_inputs, scalar_input_types and inputs2 to use arrow unary/binary for performance #12972
Removed last usages of scalar_inputs, scalar_input_types and inputs2 to use arrow unary/binary for performance #12972
Conversation
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.
LGTM, thank you @buraksenn. I wonder how CI passed before the last commit 🤔
Thanks for reviewing the PR. The reason was that in a few lines above: let mut x = &args[0]; |
x is re-set to args[1] if |
I saw that now. Then probably test case miss this. I can add further tests on this |
Thanks again @buraksenn |
Which issue does this PR close?
Closes #12923 .
Rationale for this change
Copy-pasta'ing the issue description here:
In #12881, #12890 it turned out that make_function_scalar_inputs_return_type may lead to less performant code.
In #12909 it turned out that make_function_inputs2 may lead to less performant code.
That's why this PR refactores their usages.
What changes are included in this PR?
Are these changes tested?
Existing testcases
I can add benchmarks if requested