-
Notifications
You must be signed in to change notification settings - Fork 784
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
temporal conversion functions should work on negative input properly #2326
Conversation
cb28745
to
71d2bc8
Compare
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.
The input to time32ms_to_time
etc seems to be positive, so I don't touch them.
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.
Can we revert the change to the integration test to remove negative inputs now?
}; | ||
use chrono::NaiveDateTime; | ||
|
||
#[test] |
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.
Is it worth a test of an exact number of seconds, to check the branch in split_seconds?
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.
Yea, I will add a few more tests.
yea |
Benchmark runs are scheduled for baseline = 50d1e5f and contender = 3ed0e28. 3ed0e28 is a master commit associated with this PR. Results will be available as each benchmark for each run completes. |
/// | ||
#[inline] | ||
pub(crate) fn split_second(v: i64, base: i64) -> (i64, u32) { | ||
if v < 0 { |
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.
Might be possible to simplify this using builtin div_euclid
/ rem_euclid
functions
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.
Let me try if it works. Thanks @jhorstmann
Which issue does this PR close?
Closes #2325.
Rationale for this change
What changes are included in this PR?
Are there any user-facing changes?