From 1fd8557249a9e8c04fbe7490483443ccc35dea50 Mon Sep 17 00:00:00 2001 From: Oleksandr Redko <oleksandr.red+github@gmail.com> Date: Sun, 18 Aug 2024 23:20:15 +0300 Subject: [PATCH] time: fix godoc links; remove redundant Sub mention The Time.Sub function is mentioned in the previous sentence. Change-Id: Ic79958cea4d1f9f9014f6dafd8e749c204db4f50 Reviewed-on: https://go-review.googlesource.com/c/go/+/606575 LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com> Reviewed-by: Cherry Mui <cherryyz@google.com> Reviewed-by: Ian Lance Taylor <iant@google.com> Auto-Submit: Ian Lance Taylor <iant@google.com> --- src/time/time.go | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/time/time.go b/src/time/time.go index 572ea64ccfc..0ff7faedec3 100644 --- a/src/time/time.go +++ b/src/time/time.go @@ -54,8 +54,8 @@ // On some systems the monotonic clock will stop if the computer goes to sleep. // On such a system, t.Sub(u) may not accurately reflect the actual // time that passed between t and u. The same applies to other functions and -// methods that subtract times, such as [Since], [Until], [Before], [After], -// [Add], [Sub], [Equal] and [Compare]. In some cases, you may need to strip +// methods that subtract times, such as [Since], [Until], [Time.Before], [Time.After], +// [Time.Add], [Time.Equal] and [Time.Compare]. In some cases, you may need to strip // the monotonic clock to get accurate results. // // Because the monotonic clock reading has no meaning outside -- GitLab