News for hackers. Stuff that matters.

A comment on Go: What We Got Right, What We Got Wrong. Parent comment

Re:Go: What We Got Right, What We Got Wrong by FridgeSeal on Friday January 05, 2024 @02:57AM (#38876796)
For anyone not familiar with the monotonic time issue, the implementation was found to be incorrect, and the go devs basically closed it and went “just use google smear time like we do lol, not an issue, bye”.

It did eventually get fixed I believe, but it was a shitty way of handling it.

[ Parent | on HN ]
Re:Go: What We Got Right, What We Got Wrong by masklinn on Friday January 05, 2024 @05:11AM (#38877467)
Even the "fix" is... ugh: instead of exposing monotonic time, time.Time contains both a wallclock time and an optional monotonic time, and operations update and use "the right one(s)".

Also it's not that the implementation was incorrect, it's that Go simply didn't provide access to monotonic time in any way. It had that feature internally, just gave no way to access it (hence https://github.com/golang/go/issues/16658).

[ Parent | on HN ]
Re:Go: What We Got Right, What We Got Wrong by tubthumper8 on Friday January 05, 2024 @06:05AM (#38877831)
For reference, the GitHub thread is: https://github.com/golang/go/issues/12914
[ Parent | on HN ]