Paul Dicker

Our MSRV is now 1.57, and we no longer have the time 0.1 dependency. So this change has become possible. https://github.com/chronotope/chrono/pull/1137 adds `try_*` methods besides the panicking ones, and makes...

Closing in favor of https://github.com/chronotope/chrono/issues/1127.

The `wasmbind` feature is enabled by default since https://github.com/chronotope/chrono/pull/771.

I don't think a complete migration to `core::time::Duration` is a goal anymore. It is a limited type, mostly intended for interfacing with system API's. There are advantages to having a...

Interesting, I didn't know you were working on that in the standard library.

@retrhelo Thank you for your work here! We are going in a different direction to fix this panic, see https://github.com/chronotope/chrono/issues/1127.

I agree this is worth fixing. Combining `%s%3f` to parse a millisecond timestamp is clever. On the other hand it feels just a bit too magical. An alternative is to...

The approach in this PR seems wordt persuing to me, but in a more general way. It would be nice to be able to parse `63015` to `6:30:15` with `%-H%M%S`....

Closing in favor of https://github.com/chronotope/chrono/pull/1181.

@samuelcolvin It has been a year, sorry. Would you still be available to work on this? - I don't know if it is a good idea to make a subtle...