Support for `time`

[Geobert]

With the issue chronotope/chrono#602 on chrono, I think that adding support for time directly could be usefull.

I have no doubt that chrono's case will be sort out at some point, but it highlighted that maybe, having another time representation backend could help.

It can also allow htp to be used by project that uses time and not chrono :)

If this idea is agreed on, I can volonteer to do it (no promise on how long it will take though)

[PicoJr]

Hello, thanks for the help.
I have very limited availability at the moment.

Yes I believe adding time support would be useful, I wonder if using a feature would make sense here? What do you think?

It will probably break existing API (consumers expect chrono structs) but IMO it is worth a new major release =)

[Geobert]

OK then, I'll look into it :)
It will indeed be behind a feature flag :)

I'm planning on putting current chrono support behind a feature flag, enabled by default, and add another one for time.

They will be additive, so we can have both activated if we wanted, so the API for chrono might not change at all. I'll add some wrapper to make it more explicit that it's the chrono variant, but the existing API will remain the same.

Maybe I'll add some deprecation in the worst case scenario.