Commit 67c3d4da authored by Sameer Ajmani's avatar Sameer Ajmani

time: delete incorrect docs about day-of-month checks.

Documentation was introduced by CL https://golang.org/cl/14123
but that behavior was changed later by CL https://golang.org/cl/17710.
This CL deletes the stale paragraph.

Fixes #18980

Change-Id: Ib434f1eac6fc814fde1be112a8f52afe6e3e0fcc
Reviewed-on: https://go-review.googlesource.com/36532Reviewed-by: 's avatarBrad Fitzpatrick <bradfitz@golang.org>
parent 57d06fff
...@@ -758,11 +758,6 @@ func skip(value, prefix string) (string, error) { ...@@ -758,11 +758,6 @@ func skip(value, prefix string) (string, error) {
// location and zone in the returned time. Otherwise it records the time as // location and zone in the returned time. Otherwise it records the time as
// being in a fabricated location with time fixed at the given zone offset. // being in a fabricated location with time fixed at the given zone offset.
// //
// No checking is done that the day of the month is within the month's
// valid dates; any one- or two-digit value is accepted. For example
// February 31 and even February 99 are valid dates, specifying dates
// in March and May. This behavior is consistent with time.Date.
//
// When parsing a time with a zone abbreviation like MST, if the zone abbreviation // When parsing a time with a zone abbreviation like MST, if the zone abbreviation
// has a defined offset in the current location, then that offset is used. // has a defined offset in the current location, then that offset is used.
// The zone abbreviation "UTC" is recognized as UTC regardless of location. // The zone abbreviation "UTC" is recognized as UTC regardless of location.
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment