Skip to content

Commit

Permalink
time: mention time resolution in docs
Browse files Browse the repository at this point in the history
Updates #44343
Updates #53824

Change-Id: Ia7234fac4b1b88b3c331328aaa98dc85205e09ba
Reviewed-on: https://go-review.googlesource.com/c/go/+/514275
Reviewed-by: David Chase <drchase@google.com>
TryBot-Result: Gopher Robot <gobot@golang.org>
Reviewed-by: Ian Lance Taylor <iant@google.com>
Run-TryBot: Quim Muntal <quimmuntal@gmail.com>
  • Loading branch information
qmuntal committed Aug 1, 2023
1 parent be0e0b0 commit 9138743
Showing 1 changed file with 10 additions and 0 deletions.
10 changes: 10 additions & 0 deletions src/time/time.go
Original file line number Diff line number Diff line change
Expand Up @@ -76,6 +76,16 @@
// For debugging, the result of t.String does include the monotonic
// clock reading if present. If t != u because of different monotonic clock readings,
// that difference will be visible when printing t.String() and u.String().
//
// # Timer Resolution
//
// Timer resolution varies depending on the Go runtime, the operating system
// and the underlying hardware.
// On Unix, the resolution is approximately 1ms.
// On Windows, the default resolution is approximately 16ms, but
// a lower resolution may be requested using [timeBeginPeriod].
//
// [timeBeginPeriod]: https://learn.microsoft.com/en-us/windows/win32/api/timeapi/nf-timeapi-timebeginperiod
package time

import (
Expand Down

0 comments on commit 9138743

Please sign in to comment.