> But: I expect that many of the uses of time.Now to measure elapsed time were accompanied by a comment along the lines of "// TODO: use a monotonic clock when

> But: I expect that many of the uses of time.Now to measure elapsed time were accompanied by a comment along the lines of "// TODO: use a monotonic clock when go exposes it". You may be too optimistic. I think most developers haven't heard about monotonic clocks. Cox describes this in his proposal: "Providing two APIs makes it very easy (and likely) for a developer to write programs that fail only rarely, but typically all at the same time."