Facebook
Google
GitHub
Linkedin
That magical period where adding a Duration to a timestamp can yield a different time than adding a number of seconds.
I see some minor graphing spacetime
glitches (line discontinuities) at switching from it but nothing major in my current energy tracking project. The internal time is in UTC while user presentations are using local times.
One more corner-case to think about.
Example: https://github.com/tidyverse/lubridate/issues/759
https://www.loc.gov/standards/datetime/iso-tc154-wg5_n0038_iso_wd_8601-1_2016-02-16.pdf
4.2.2.1 General
In the representations of local time as defined below no provisions have been made to prevent
ambiguities in expressions that result from discontinuities in the time scale of local time (e.g. daylight
saving time). When an application identifies the need to prevent these ambiguities, use can be made of
the provision of 4.2.5.2.
I see some minor graphing spacetime
glitches (line discontinuities) at switching from it but nothing major in my current energy tracking project. The internal time is in UTC while user presentations are using local times.One more corner-case to think about.
Example: https://github.com/tidyverse/lubridate/issues/759
https://www.loc.gov/standards/datetime/iso-tc154-wg5_n0038_iso_wd_8601-1_2016-02-16.pdf
4.2.2.1 General
In the representations of local time as defined below no provisions have been made to prevent
ambiguities in expressions that result from discontinuities in the time scale of local time (e.g. daylight
saving time). When an application identifies the need to prevent these ambiguities, use can be made of
the provision of 4.2.5.2.
Last edited:
