-
Notifications
You must be signed in to change notification settings - Fork 791
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
Fix clippy by avoiding deprecated functions in chrono #3096
Conversation
6cdb556
to
8936cbd
Compare
Benchmark runs are scheduled for baseline = 94565bc and contender = ccc4417. ccc4417 is a master commit associated with this PR. Results will be available as each benchmark for each run completes. |
|
||
assert_eq!(shift_months(base, 0), base); | ||
assert_eq!(shift_months(base, 1), NaiveDate::from_ymd(2021, 1, 31)); |
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 feels very familiar / similar to the work in https://github.com/apache/arrow-datafusion/pull/4189/files#diff-880863b84a09b210db1fc00012b1f3fbf0ade7f23c4297e15b54474ec65cb814R107
I'll see if I can find a way to remove the copy in DataFusion
Thanks @viirya |
Can drop this after rebase on commit ccc4417 "Fix clippy by avoiding deprecated functions in chrono (apache#3096)", first released in 28.0.0
Can drop this after rebase on commit ccc4417 "Fix clippy by avoiding deprecated functions in chrono (apache#3096)", first released in 28.0.0
Can drop this after rebase on commit ccc4417 "Fix clippy by avoiding deprecated functions in chrono (apache#3096)", first released in 28.0.0
Can drop this after rebase on commit ccc4417 "Fix clippy by avoiding deprecated functions in chrono (apache#3096)", first released in 28.0.0
Can drop this after rebase on commit ccc4417 "Fix clippy by avoiding deprecated functions in chrono (apache#3096)", first released in 28.0.0
Which issue does this PR close?
Closes #3097.
Rationale for this change
What changes are included in this PR?
Are there any user-facing changes?