chore: use chrono::DateTime::from_timestamp in utc_now#128
Merged
Conversation
DateTime::from_timestamp already returns DateTime<Utc>; the round-trip through naive_utc and from_naive_utc_and_offset is unnecessary.
piscisaureus
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
NaiveDateTime::from_timestamp_opt is deprecated since chrono 0.4.35;
DateTime::from_timestamp replaces it directly and already returns
DateTime, removing the naive round-trip. Applies to the three
identical time.rs copies in proto, remote, and sqlite.