Truncating a timestamp close to EPOCH fails about chrono

[djc]

I'd be happy to review a PR -- I probably won't have time to work on this myself.

[joroKr21]

It's not urgent for me but I think I will find time for it

[pitdicker]

To be honest in my opinion the API and approach in the round module is fundamentally flawed. A lot of the behavior doesn't make sense, especially for a library that tries to do handle dates and timezones correctly like chrono. And I don't think it is even possible to fix all logic bugs.

But we would need to have an alternative before it can be deprecated.

[djc]

But we would need to have an alternative before it can be deprecated.

Why? If we think this API is silly or wrong or dangerous, we could deprecate it without providing an alternative.

Does the time crate provide this functionality?

[pitdicker]

There are some cases where it works and gives correct results. For example rounding or truncating a NaiveTime to a reasonable Duration such as 10 seconds. But rounding to for example 7 seconds, and especially when involving dates becomes a mess. And that is ignoring DST 😄.

Why? If we think this API is silly or wrong or dangerous, we could deprecate it without providing an alternative.

Maybe you are right. It does not really feel like an inconvenience yet, but we can expect more issues like this.

Does the time crate provide this functionality?

It doesn't seem to.

[pitdicker]

Another issue with duration_trunc: #584.