Remove redundant unwrap in ScalarValue::new_primitive, return a Result #7830
Conversation
maruschin
changed the title
alamb
left a comment
alamb
left a comment
There was a problem hiding this comment.
This looks good to me -- while it is an API change I think it is a reasonable one. Thank you @maruschin
I noticed the comments also need to be updated but we could also do that as a follow on PR as well
| a: Option<T::Native>, | ||
| d: &DataType, | ||
| ) -> Self { | ||
| ) -> Result<Self> { |
There was a problem hiding this comment.
I think the comments in this function also need to be updated (the 'panic's section is no longer correct)
/// Create a [`ScalarValue`] with the provided value and datatype
///
/// # Panics
///
/// Panics if d is not compatible with T
There was a problem hiding this comment.
with_data_type can still panic, I personally don't see anything wrong with this FWIW, panic are a perfectly valid way to handle unexpected failure imo
There was a problem hiding this comment.
Wrong with what? As in it is fine if this function panics and there is no need to propagate the error?
There was a problem hiding this comment.
Its an exceptional case that would imply some sort of schema inconsistency within the running plan, so imo panicking is perfectly valid, but then so is returning an error. The broader point is the doc is still correct
There was a problem hiding this comment.
I understand the point about the panics -- thank you
I don't have a strong opinion either way with regards to propagating errors vs panic'ing
alamb
changed the title
ScalarValue::new_primitive
alamb
changed the title
ScalarValue::new_primitiveScalarValue::new_primitive, return a Result
|
Thanks @maruschin |
4 participants
Which issue does this PR close?
It's a part of #3313.
Rationale for this change
What changes are included in this PR?
Are these changes tested?
Are there any user-facing changes?