Skip to content
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

time: behavior of function Parse for Feburary 31 #18980

dmage opened this issue Feb 7, 2017 · 1 comment

time: behavior of function Parse for Feburary 31 #18980

dmage opened this issue Feb 7, 2017 · 1 comment


Copy link

@dmage 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?

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
but that behavior was changed later by CL

@ALTree ALTree added this to the Go1.9 milestone Feb 7, 2017
@Sajmani Sajmani self-assigned this Feb 7, 2017
Copy link

@gopherbot gopherbot commented Feb 7, 2017

CL mentions this issue.

@gopherbot gopherbot closed this in 67c3d4d Feb 7, 2017
@golang golang locked and limited conversation to collaborators Feb 7, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
4 participants
You can’t perform that action at this time.