Programmers will be happy to hear that the BIPM has abolished all future
leap seconds [1][2] in favor of putting off the problem for a few
thousand years (when UTC and solar time disagree by an hour). It’s our
descendant’s problem now!

The issue was that we were going to have a negative leap second[3],
which was something nobody was prepared for. The SRFI 285 sample
implementation attempts to account for it, but now that code (and the
verbiage that mentions it) is redundant.

[1]:
https://www.theguardian.com/science/2026/oct/15/times-up-for-the-leap-second-as-scientists-swap-it-for-the-leap-hour
[2]: https://www.bipm.org/en/cgpm-2026/resolution-5
[3]: https://groups.io/g/LEAPSECS/message/16

-- Peter McGoron