So what&#x27;s a better time library?
Or, rather, how could Go&#x27;s time library better accommodate these things?
It&#x27;s also not clear that a standard library time package should be the be-all, end-all time management solution. I don&#x27;t see any reason for a standard time package to handle historical dates, for example.<p>Google found a nice solution to the leap second issue: we &quot;smear&quot; the second over the day before it occurs by making tiny changes to the time over the day. This means user applications don&#x27;t need to be aware of it: <a href="http:&#x2F;&#x2F;googleblog.blogspot.com.au&#x2F;2011&#x2F;09&#x2F;time-technology-and-leaping-seconds.html" rel="nofollow">http:&#x2F;&#x2F;googleblog.blogspot.com.au&#x2F;2011&#x2F;09&#x2F;time-technology-an...</a>