@wycats What about time zone changes that are not a full hour? Would that apply in your use case?
-
-
-
@percyhanna "1 hour" is "1 hour" regardless of time zone changes for most people. "1 day" is actually ambiguous. "1 hour from now" ambiguous
End of conversation
New conversation -
-
-
@wycats according to a standard or...? I remember you working on that date time lib for rust ages back. -
@colemickens According to reality :) Leap seconds!
End of conversation
New conversation -
-
-
@wycats But a minute can have 61 seconds due to leap-seconds (hence the possible seconds range of 0–60 rather than 0–59). -
@__chrismorgan I'm being a bit pedantic I think. When people do Duration::minutes(1), they mean 60s. ::weeks()… unknown
End of conversation
New conversation -
-
-
@wycats what about leap seconds? They can make minutes, hours, etc longer. http://en.m.wikipedia.org/wiki/Leap_second … -
@ktheory Leap seconds can't make "1 hour" longer. They make "1 day" have an unknown number of seconds.
End of conversation
New conversation -
-
-
@wycats I'm trying to remember why not days? -
@ryantablada Leap seconds.
End of conversation
New conversation -
-
-
@wycats Leap seconds change seconds/minutes/hours. -
@ethangunderson They affect "one minute from now", but do not change the meaning of "one minute" -
@wycats Ah, good point.
End of conversation
New conversation -
-
-
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
@wycats Leap seconds are usually put as 61st second eg. 23:59:60 So you could argue that that minute is 61 seconds long.Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.