SE-0329: Clock, Instant, Date, and Duration

[Tino]

@Jean-Daniel

Can you elaborate on why clock.now + .hours(3) is not a proper way to express a time 3 hours from now ?

There's some more discussion about the topic:

[Pitch] Clock, Instant, Date, and Duration

I finally articulated this morning why I've got an issue with the proposed Duration, thanks to your post @Tino: The unit is ambiguous. There are two kinds of durations we deal with: physical seconds and clock seconds. Most of the time these are equivalent, but they do not have to be. Past Clocks A bunch of historical clocks had variable length seconds, because the length of a second was derived based on how much daylight there was that day. So if anyone wanted to implement a historical clock…

and for issues like this

@divanise

As I understand the proposal, that's not an option when setting a deadline for operations across distributed systems. Only WallClock is defined in a way to be meaningful in that case.

there are some thoughts in Clock synchronization - #8 by Tino (I'm not sure about results... but so far, I'm still convinced that system time alone is not a good choice for timeouts in distributed contexts)