Paul Dicker
Paul Dicker
This PR touches a lot of lines, but I would only call the first 5 commits and the last one interesting. - In a few places that only work with...
*Part of this has been discussed before in #716 and #1049, and was my motivation to start contributing to chrono in #1017.* The calculation to go from a local time...
This is the first part of #1418 and applies to the branch for 0.4.x. We have two small bugs in our implementation of `Parsed`: * If there is a timestamp...
Chrono would become more correct and convenient if the `Datelike` and `Timelike` traits were removed in 0.5. I propose to implement their methods directly on the types that currently implement...
Every (de)serializer we have for use with `serde_with` comes with a lot of boilerplate. Each needs two modules (for a regular and optional variant), `serialize` and `deserialize` methods, a `Visitor`...
The following methods can panic and have a `try_` variant: ```rust impl Duration { pub const fn weeks(weeks: i64) -> Duration; pub const fn days(days: i64) -> Duration; pub const...
RFC 3339 and RFC 2822 make a distinction between an offset of `+00:00` and `-00:00`. RFC 2822: > The form "+0000" SHOULD be used to indicate a time zone at...
This issue is basically the opposite of #660. My use cases for parsing with chrono have until now been to parse dates in whatever format they are given by users...
With our strftime syntax it is possible to specify padding (zero padding `%0?`, spaces as padding `%_?`, no padding at all `%-?`, or the default). This maps to three variants...
This issue is not meant to complain, but to discuss a problem that in my opinion we have with our process. Doing trivial changes is going great. Over the past...