Paul Dicker

Closing because we don't have the information to reproduce, have reported it upstream (the standard library), and have https://github.com/chronotope/chrono/issues/1250 to discuss if we want to expose the platform capabilities in...

I reopened the related issue https://github.com/chronotope/chrono/issues/38 because it is older and has some useful discussion. Closing this one as a duplicate.

Fixed in https://github.com/chronotope/chrono/pull/1337.

> I think this would have to come with a very strong rationale for why (something like) this is the best possible design. I don't think it fits very well...

To comment on this PR: I would add just one standalone public function in the `offset` module, which can serve to set and clear the override: ```rust pub fn override_now(datetime:...

@jtmoon79 I planned on taking over this PR next week, but maybe it is more your cup of tea?

https://github.com/chronotope/chrono/pull/1244 is the updated PR.

Closing due to inactivity.

This currently works as documented. ```rust /// Returns the second number from 0 to 59. fn second(&self) -> u32; /// Returns the number of nanoseconds since the whole non-leap second....

In today's chrono you can do this with: ```rust Local::now().set_time(NaiveTime::MIN).unwrap(); ``` Because `Local::today()` and `Date` are deprecated, I don't see `Date::and_second_from_midnight` getting implemented.