qbit/go
1
0
Fork 0
mirror of https://github.com/golang/go synced 2024-11-18 01:34:44 -07:00
Code Releases Activity

time: fix example in monotonic time comment

Browse Source 
t.Sub(u) would be -20 milliseconds.
The right computation is u.Sub(t), but rewrite to be even clearer.

Thanks to Karsten Weiss for catching this.

Change-Id: I6e274d69b0301840d57c5c65bf4114da0d33bf10
Reviewed-on: https://go-review.googlesource.com/46971
Run-TryBot: Russ Cox <rsc@golang.org>
TryBot-Result: Gobot Gobot <gobot@golang.org>
Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
This commit is contained in:
Russ Cox 2017-06-28 10:33:15 -04:00 committed by Brad Fitzpatrick
parent 1a56a27c58
commit 5e585830d3
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
src/time/time.go
View File

@ -23,10 +23,10 @@
// approximately 20 milliseconds, even if the wall clock is changed during
// the operation being timed:
//
// t := time.Now()
// start := time.Now()
// ... operation that takes 20 milliseconds ...
// u := time.Now()
// elapsed := t.Sub(u)
// t := time.Now()
// elapsed := t.Sub(start)
//
// Other idioms, such as time.Since(start), time.Until(deadline), and
// time.Now().Before(deadline), are similarly robust against wall clock