Paul Dicker

Oops, replied on the wrong issue. Copying here. (Not a reply, just some things I'm thinking about.) ### Summer and winter time The concepts of 'daylight saving time', 'standard time',...

> Can you link to the requests you've seen for this so we can get the full detail of the use cases (to the extent provided)? :+1: After searching for...

> Correctness and precision are not exactly the same thing, and it feels to me like you're chasing a level of precision here the requirement for which might be extremely...

Added another commit to remove some duplicated length checks. They where just before `scan::nanosecond_fixed`, which uses `scan::number` that does the same checks.

Thank you! What errors would this catch that our regular build and test CI runs don't catch?

Just added a similar CI job for chrono-tz in https://github.com/chronotope/chrono-tz/pull/158. So I now see its use :smile:. @jtmoon79 Want to finish up this PR?

(Not a reply, just some things I'm thinking about.) ### Summer and winter time The concepts of 'daylight saving time', 'standard time', 'summer time' and 'winter time' are related but...

> Can you link to the requests you've seen for this so we can get the full detail of the use cases (to the extent provided)? :+1: After searching for...

Sorry, replied in the wrong issue. Yes, I would only like to see a `LocalOffset` with nothing else for 0.5. The rest would not be a breaking change.

This crate compiles the time zone data into a large table of transitions for a fixed set of years. The data doesn't include a TZ string like TZif files have.