Paul Dicker
Paul Dicker
Not sure what the exact issue is to reply to, but I'll try writing something. I think supporting `no_std` certainly added quite some trouble for Rand. And it is not...
Please open an issue against chrono if there is something we can do to help on our side.
> That makes it very tricky to review. Yes, I realize that :disappointed:. Maybe I can split it in: - Drop the existing caching logic, and move all time zone...
I'll see what I can do to split it up more.
Setting to draft for now. This is only tangentially related to the work of converting the API to `Result`s. I'll concentrate on the `time_delta` and parsing modules first.
We now Have `TryFrom` and the MSRV is 1.56, so this issue seems completed.
I believe this issue can be closed, there is nothing to do here.
While https://github.com/chronotope/chrono/issues/1150 is a duplicate of this issue, it becomes a bit more specific on what to fix. Closing this issue as a duplicate.
So the issue is that RFC 3339 doesn't support dates beyond 0..=9999. I opened https://github.com/chronotope/chrono/pull/1144 to replace `to_rfc3339()` with `to_iso8601` (which does support arbitrary years if preceded by a sign)...
I played with this PR, hoping to help push it over the finish line now that our MSRV is 1.56 and 1.57 is maybe possible. But I now think it...