refactor: use jiff for safer time features
#10118
Merged
+132
−172
Conversation
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
aaron-ang
force-pushed
the
migrate-jiff
branch
2 times, most recently
from
f51c99e to
6bc9b7f
Compare
aaron-ang
force-pushed
the
migrate-jiff
branch
from
6bc9b7f to
6a84481
Compare
|
GNU testsuite comparison: |
sylvestre
reviewed
Jan 8, 2026
| ("-1 hours", Duration::hours(1)), | ||
| ("-1 day", Duration::days(1)), | ||
| ("-2 weeks", Duration::weeks(2)), | ||
| ("-1 hour", 1.hours()), |
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.
Inspired when working on PR #10093. We shouldn't have to mix
chronowithjiff, especially since https://github.com/uutils/parse_datetime is already integrated withjiff.