cybercyst/go
1
0
Fork 0
mirror of https://github.com/golang/go.git synced 2025-05-05 15:43:04 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Missing "rare", I think

Will Faught 2022-08-18 20:00:02 -07:00
parent aac5882e3a
commit e7f20f830b
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
CodeReviewConcurrency.md

@ -191,7 +191,7 @@ Quoting the [documentation for `time.Time`](https://pkg.go.dev/time/#Time):
from `t`?** This is a consequence of the previous item. If the monotonic component is stripped from from `t`?** This is a consequence of the previous item. If the monotonic component is stripped from
the `time.Time` structure before passing it into `time.Since()` function (via calling either the `time.Time` structure before passing it into `time.Since()` function (via calling either
`UTC()`, `Local()`, `In()`, `Round()`, `Truncate()`, or `AddDate()`) **the result of `time.Since()` `UTC()`, `Local()`, `In()`, `Round()`, `Truncate()`, or `AddDate()`) **the result of `time.Since()`
might be negative** on very occasions, such as if the system time has been synced via NTP between might be negative** on very rare occasions, such as if the system time has been synced via NTP between
the moment when the start time was originally obtained and the moment when `time.Since()` is called. the moment when the start time was originally obtained and the moment when `time.Since()` is called.
If the monotonic component is *not* stripped, `time.Since()` will always return a positive duration. If the monotonic component is *not* stripped, `time.Since()` will always return a positive duration.