We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
When compiling a package containing import "./sub":
import "./sub"
$ vgo build . vgo: resolving import "./sub" FindRepo: Get https://./sub?go-get=1: dial tcp: lookup .: no such host vgo: import "github.com/neild/test" -> import "./sub": Get https://./sub?go-get=1: dial tcp: lookup .: no such host
I have no opinion on whether vgo should support relative imports, but it probably should at least recognize them.
The text was updated successfully, but these errors were encountered:
Or this could be the chance to kill them.
Sorry, something went wrong.
but it probably should at least recognize them.
Agreed. Enough to say "no", rather than tcp: lookup .: no such host
tcp: lookup .: no such host
They're definitely not supposed to work, but they're not supposed to fail that badly. :-)
(They don't work from within GOPATH today even with the standard go command.)
Change https://golang.org/cl/108378 mentions this issue: cmd/go/internal/vgo: vgo does not support relative imports
cmd/go/internal/vgo: vgo does not support relative imports
golang/vgo@f663b31
No branches or pull requests
When compiling a package containing
import "./sub"
:I have no opinion on whether vgo should support relative imports, but it probably should at least recognize them.
The text was updated successfully, but these errors were encountered: