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: no Parse in a specific Location #3653

Closed
rsc opened this issue May 22, 2012 · 5 comments
Closed

time: no Parse in a specific Location #3653

rsc opened this issue May 22, 2012 · 5 comments
Milestone

Comments

@rsc
Copy link
Contributor

rsc commented May 22, 2012

Parse uses Local.  Should there be a ParseInLocation or something like that that lets
you pass in a *Location to use instead of Local?
@rsc
Copy link
Contributor Author

rsc commented Sep 12, 2012

Comment 1:

Labels changed: added go1.1maybe.

@rsc
Copy link
Contributor Author

rsc commented Dec 10, 2012

Comment 2:

Labels changed: added size-m.

@rsc
Copy link
Contributor Author

rsc commented Feb 3, 2013

Comment 3:

Labels changed: added go1.1, removed go1.1maybe.

@bradfitz
Copy link
Contributor

bradfitz commented Feb 3, 2013

Comment 4:

Is this as simple as https://golang.org/cl/7278049 ?

@rsc
Copy link
Contributor Author

rsc commented Feb 4, 2013

Comment 5:

This issue was closed by revision 1d9f67d.

Status changed to Fixed.

@rsc rsc added fixed labels Feb 4, 2013
@rsc rsc self-assigned this Feb 4, 2013
@rsc rsc added this to the Go1.1 milestone Apr 14, 2015
@rsc rsc removed the go1.1 label Apr 14, 2015
@golang golang locked and limited conversation to collaborators Jun 24, 2016
@rsc rsc removed their assignment Jun 22, 2022
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants