Paul Dicker

Better to make the range a full year smaller. Having the minimum date be January 2 and the maximum date December 30 is just strange.

A lot of the work to fix this has already been completed. Groundwork was done in #1310, #1313, #1069 and #1312, and fixes landed in #1070, #1317 and #1071. Only...

Thank you for the good suggestions! I will add new commits to address review comments, and can squash them before later.

Ai, why do you have to ask that :rofl: ? As a hobby I am making my own feed reader, and I would like to know the time an entry...

As a better reason: we would follow the RFCs more closely, and be able to round-trip these timestamps.

That is fair. Honestly the changes felt small, so i did some counting: - 17 lines for testing the size of common types in chrono. - 30 would also be...

*Finally* updated. Sorry to let this linger for 3+ months.

> Can you find an appropriate docstring to place this information (especially the quoted RFC stuff)? This is a great explanation of little finicky area that I suspect quite a...

> Interestingly, this was a common case that was causing failures in [`tests/dateutils.rs::verify_against_date_command_format_local`](https://github.com/chronotope/chrono/blob/0a16a655416b07e011d9f10de24220103be7044a/tests/dateutils.rs#L79), if this is merged, we may be able to ensure the offsets match as well, rather than...

I would like to start working on 0.5 in earnest in the next couple of weeks. But I really want to avoid some ugly merge conflicts with open PRs, which...