-
Notifications
You must be signed in to change notification settings - Fork 4k
GH-35560: [C++] Use Cast() instead of CastTo() for Scalar in test #39044
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
Conversation
|
|
393021d to
d5d26d1
Compare
kou
left a comment
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.
+1
|
|
fb31c68 to
a9a7d0d
Compare
|
Hello, @kou I resolved a conflict that arose due to a commit related to timestamp casting. |
|
After merging your PR, Conbench analyzed the 6 benchmarking runs that have been run so far on merge-commit 7ccf6fd. There were no benchmark performance regressions. 🎉 The full Conbench report has more details. It also includes information about 1 possible false positive for unstable benchmarks that are known to sometimes produce them. |
…st (apache#39044) ### Rationale for this change Remove legacy code ### What changes are included in this PR? * Replace the legacy scalar `CastTo` implementation with the new cast compute kernel for supported types, without requiring additional casting logic for unsupported types. ### Are these changes tested? Yes. It is passed by existing test cases. ### Are there any user-facing changes? No. * Closes: apache#35560 Authored-by: Hyunseok Seo <hsseo0501@gmail.com> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
Rationale for this change
Remove legacy code
What changes are included in this PR?
CastToimplementation with the new cast compute kernel for supported types, without requiring additional casting logic for unsupported types.Are these changes tested?
Yes. It is passed by existing test cases.
Are there any user-facing changes?
No.