Lofitime: A hifitime <-> chrono adapter #31
Merged
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.
Egui uses chrono for displaying dates and times, but I want to use hifitime for all of my internal timings. To adapt between chrono and hifitime datetimes and durations, I created a new crate called
lofitime
.lofitime
adds a few traits that bridge the gap. I even wrote tests that pass!NOTE: For convenience,
chrono
->hifitime
conversions are truncated to the millisecond.hifitime
->chrono
conversions use all of chrono's available precision.hifitime::Epoch
chrono::DateTime<Utc>
HifiDateTime
.to_lofi_utc()
hifitime::Epoch
chrono::NaiveDateTime
HifiDateTime
.to_lofi_naive()
hifitime::Duration
chrono::Duration
HifiDateTime
.to_lofi_duration()
chrono::DateTime
orchrono::NaiveTime
hifitime::Epoch
LofiDateTime
.to_hifi_epoch()
chrono::DateTime
orchrono::NaiveTime
hifitime::Epoch
LofiDateTime
.to_hifi_duration()
This PR also contains some quality of life improvements like disabling CI workflows that are doomed to fail.