-
Notifications
You must be signed in to change notification settings - Fork 1.8k
minor: refactor with assert_or_internal_err!() in datafusion/functions
#18700
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
minor: refactor with assert_or_internal_err!() in datafusion/functions
#18700
Conversation
| assert_or_internal_err!( | ||
| lhs.len() == rhs.len(), | ||
| "All arrays should have the same length for greatest comparison" | ||
| ); |
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.
Should be using assert_eq_or_internal_err?
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.
Yes, you are right I should have done that.
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.
Changed it.
| ); | ||
| } | ||
| assert_or_internal_err!( | ||
| lhs.len() == rhs.len(), |
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.
This can also be changed
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.
Sure
2010YOUY01
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.
Thank you!
Which issue does this PR close?
assert_or_internal_err!()across the codebase #18613Rationale for this change
What changes are included in this PR?
Are these changes tested?
Are there any user-facing changes?