On Fri, 22 Aug 2025 at 16:41, Jonathan Wakely <jwakely....@gmail.com> wrote: >> It marks tai_clock and gps_clock "is_steady = true", as they >> are not subject to adjudicated discontinuities, unlike civil >> time with annual spring and fall changes, and UTC with > > > Please revert this part. is_steady has nothing to do with civil time or > daylight savings transitions.
Right. A steady clock could be used in an implementation of a tai_clock or a gps_clock, but tai_clock and gps_clock aren't required to be steady. They aren't required to fulfil either of the two requirements for a steady clock, and our implementations likely don't. They don't go backwards because of a daylight savings adjustment, but can go backwards for other (non-adjudicated) reasons. Their tick likely isn't completely constant.
