Sept. 1, 2016
7:43 p.m.
On Sep 1, 2016, at 3:08 PM, John Hawkinson <jhawk@mit.edu> wrote:
On Aug. 8, Paul remarked that he expected an October release would be the first to incorporate the leap second changes for this December. That is 2 months; that is not a comfortable amount of time.
I second the notion that leap second updates should be accompanied with a greater sense of urgency. My library provides leap-second-aware clocks which should be accurate within a second 5 months into the future. https://howardhinnant.github.io/date/tz.html#utc_clock https://howardhinnant.github.io/date/tz.html#tai_clock https://howardhinnant.github.io/date/tz.html#gps_clock Howard