Skip to content

time: fix another 400 year offset in comment #21043

@markus-oberhumer

Description

@markus-oberhumer

Found by inspecting time/time.go after reading Russ' recent Go Blog entry.

Looks like an oversight in git commit d93f3b5 .

What version of Go are you using (go version)?

Current go 1.9.x-git 504deee .

What did you do?

$ git diff 504deee6088c2448fc3e91c94a1ba69ec92fb7ef
diff --git a/src/time/time.go b/src/time/time.go
index 0a83543e8a..8a29eef263 100644
--- a/src/time/time.go
+++ b/src/time/time.go
@@ -370,7 +370,7 @@ func (d Weekday) String() string { return days[d] }
 // everywhere.
 //
 // The calendar runs on an exact 400 year cycle: a 400-year calendar
-// printed for 1970-2469 will apply as well to 2370-2769. Even the days
+// printed for 1970-2369 will apply as well to 2370-2769. Even the days
 // of the week match up. It simplifies the computations to choose the
 // cycle boundaries so that the exceptional years are always delayed as
 // long as possible. That means choosing a year equal to 1 mod 400, so

Metadata

Metadata

Assignees

No one assigned

    Labels

    DocumentationIssues describing a change to documentation.FrozenDueToAgeNeedsFixThe path to resolution is known, but the work has not been done.

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions