Skip to content

time: behavior of function Parse for Feburary 31 #18980

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
dmage opened this issue Feb 7, 2017 · 1 comment
Closed

time: behavior of function Parse for Feburary 31 #18980

dmage opened this issue Feb 7, 2017 · 1 comment
Labels
Documentation Issues describing a change to documentation. FrozenDueToAge NeedsFix The path to resolution is known, but the work has not been done.
Milestone

Comments

@dmage
Copy link
Contributor

dmage commented Feb 7, 2017

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

go version go1.7.5 darwin/amd64

What did you do?

https://play.golang.org/p/R4HlVseTm2

What did you expect to see?

A behavior which corresponds the documentation.

Actually I expect to see an error, but the current documentation says that it should be parsed successfully.

For example February 31 and even February 99 are valid dates, specifying dates in March and May.

Documentation was introduced by CL https://golang.org/cl/14123
but that behavior was changed later by CL https://golang.org/cl/17710

@ALTree ALTree added Documentation Issues describing a change to documentation. NeedsFix The path to resolution is known, but the work has not been done. labels Feb 7, 2017
@ALTree ALTree added this to the Go1.9 milestone Feb 7, 2017
@Sajmani Sajmani self-assigned this Feb 7, 2017
@gopherbot
Copy link
Contributor

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

@golang golang locked and limited conversation to collaborators Feb 7, 2018
@rsc rsc unassigned Sajmani Jun 23, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Documentation Issues describing a change to documentation. FrozenDueToAge NeedsFix The path to resolution is known, but the work has not been done.
Projects
None yet
Development

No branches or pull requests

4 participants