time: Unix(sec, nanonsec) has bizarre undocumented behavior for large values of sec

[maxpoletto]

The biggest value that can be passed as the first parameter of time.Unix(seconds, nanos) is
math.MaxInt64 - 62135596800. Sample code: http://play.golang.org/p/Ck5Ny1W-ud

62135596800 is the number of seconds, accounting for leap days, that separate the start of the Go internal epoch (year 1) from the start of the Unix epoch (1970).

time.Unix() should not leak its implementation details in this way, or else the behavior should be clearly documented.

It does not seem unreasonable, given the current spec/docs, for someone to create a time.Unix(math.MaxInt64, 0) as a sentinel value, but this leads to strange and hard-to-debug behavior.

[minux]

time.Unix(math.MaxInt64, 0) is expecting too much from the undocumented implementation. The internal epoch value is intentionally not publicly documented.

[gopherbot]

CL https://golang.org/cl/10223 mentions this issue.

[gopherbot]

CL https://golang.org/cl/10266 mentions this issue.