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

Jump to bottom

cmd/go: Remove support for relative import paths. #6147

Closed
mewmew opened this issue Aug 14, 2013 · 5 comments
Closed

cmd/go: Remove support for relative import paths. #6147

mewmew opened this issue Aug 14, 2013 · 5 comments
Labels
FrozenDueToAge Thinking
Milestone
Unplanned

Comments

@mewmew
Copy link
Contributor

mewmew commented Aug 14, 2013 

Ref the discussion at golang-nuts "Proposal: ban relative import paths".

https://groups.google.com/d/msg/golang-nuts/n9d8RzVnadk/07f9RDlwLsYJ

Posted by Andrew Gerrand on Apr 3:
> See my earlier post in this thread about why relative imports are a bad idea.
> 
> The only reason the go tool supports relative imports is to run the compiler tests,
which predate the go tool and the concept of GOPATH. I would prefer to refactor the
compiler tests so that relative imports are not used, and remove support for relative
imports from the go tool entirely.
> 
> Andrew
@rsc
Copy link
Contributor

rsc commented Aug 14, 2013

Comment 1:

Unclear whether this is really something we should do. Certainly not for Go 1.2.
I find relative imports very useful for simple tests, and I will be sad if I cannot 'go
run' those tests.

Labels changed: added priority-someday, removed priority-triage, go1.2maybe.

Status changed to Thinking.

@rsc
Copy link
Contributor

rsc commented Nov 27, 2013

Comment 2:

Labels changed: added go1.3maybe.

@rsc
Copy link
Contributor

rsc commented Dec 4, 2013

Comment 3:

Labels changed: added release-none, removed go1.3maybe.

@rsc
Copy link
Contributor

rsc commented Dec 4, 2013

Comment 4:

Labels changed: added repo-main.

@neelance neelance mentioned this issue Jan 7, 2015
Closed
@rsc rsc added this to the Unplanned milestone Apr 10, 2015
@rsc
Copy link
Contributor

rsc commented Apr 20, 2015

I believe we should keep the limited support that exists today.

@rsc rsc closed this as completed Apr 20, 2015
@ThisGuyCodes ThisGuyCodes mentioned this issue Mar 7, 2016
Closed
@akavel akavel mentioned this issue Jun 23, 2016
Closed
@golang golang locked and limited conversation to collaborators Jun 24, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
FrozenDueToAge Thinking
Projects
None yet
Milestone
Unplanned
Development

No branches or pull requests
3 participants
@rsc @mewmew @gopherbot