Paul Dicker

For `Duration` I opened https://github.com/chronotope/chrono/pull/1327, and https://github.com/chronotope/chrono/pull/1286 is quite small I think. I'll work on splitting up the third.

@Ekleog Thank you so much for digging into this issue! And you put your money where your mouth is with your [kine crate](https://crates.io/crates/kine). As a first note: while I personally...

Adding a `Tai` timezone as suggested in the documentation, so that it is possible to convert between `DateTime` and `DateTime`, seems like a good first step. Then arithmetic can work...

> 1/86400th of a day; and a day is defined based on the movement of the Earth, this duration fluctuates over time (a historical second measured 100 years ago or...

https://github.com/chronotope/chrono/pull/1279 added `DateTime::::from_timestamp`, which partly fixes this issue. I would like to keep this open to track renaming `TimeZone::timestamp`.

@WhyNotHugo Sorry, I did not read closely enough, and thought this was solved. > Fox context: I'm parsing icalendar objects, and some fields (like recurrence dates of events) can have...

Had a number of months to think about this, and closing again. As written in the previous post we have basically two options: 1. Make the `TimeZone` or `Offset` traits...

On second thought: We could potentially let some `Offset::update_for_local_datetime` method return a `LocalResult`, and you would have to call a second method to get the second variant in case the...

To add as a use case: Chrono may be used as a dependency by some crate with `default-features = false, features = "arbitrary"`. For chrono that implies `no_std`. Should the...

Last year I did some calculations on the minimum size needed for a `TzOffset`. It currently has the definition: ```rust pub struct TzOffset { tz: Tz, // ~600 variants so...