<story><title>Proposal: Monotonic Elapsed Time Measurements in Go</title><url>https://github.com/golang/proposal/blob/master/design/12914-monotonic.md</url></story><parent_chain></parent_chain><comment><author>jkn</author><text>This a pretty magical solution.&lt;p&gt;- Backward compatible. No API change.&lt;p&gt;- Naive, idiomatic and wrong use of the API automatically becomes naive, idiomatic and correct: Existing code that was using wall-clock time will now be using monotonic time when it should, and only when it should [1]&lt;p&gt;- No change to the memory footprint on 64-bit systems&lt;p&gt;- No change to the range of representable dates [2]&lt;p&gt;&amp;quot;No API change&amp;quot; means if for some reason it turns out to be a bad idea, they can still revert it and stay backward compatible (though of course, the documentation will mention how monotonic times are used to calculate better time differences and that would no longer be true after a revert).&lt;p&gt;Very impressed with the extensive survey of existing code which didn&amp;#x27;t find a single case where the change would cause an issue.&lt;p&gt;[1] Except when a user got out of their way to calculate a time difference in a non-idiomatic way.&lt;p&gt;[2] The range is only restricted when monotonic time information is present, which cannot sensibly be the case outside the restricted range.</text></comment>
<story><title>Proposal: Monotonic Elapsed Time Measurements in Go</title><url>https://github.com/golang/proposal/blob/master/design/12914-monotonic.md</url></story><parent_chain></parent_chain><comment><author>knodi</author><text>Well written and an excellent in-depth break down of the problem and solution(s). Would have expect nothing but excellence from Russ Cox.</text></comment>