Filed https://golang.org/issue/34628
On Fri, 2019-09-27 at 15:19 +0930, Dan Kortschak wrote:
> Looking into it it appears that there's active work in
> go/build.defaultGOPATH that makes returning an informative error
> message impossible.
>
> This made sense when it was done in 428df5e39c0[1],
Looking into it it appears that there's active work in
go/build.defaultGOPATH that makes returning an informative error
message impossible.
This made sense when it was done in 428df5e39c0[1], but since then
57568958774[2] has gone in which changes the message from something
that was useful to
Yes, that explains it. Perhaps the error could be more informative.
On Thu, 2019-09-26 at 20:19 -0700, Ian Lance Taylor wrote:
> On Thu, Sep 26, 2019 at 7:36 PM Dan Kortschak
> wrote:
> >
> > I am looking at some changes we have made to make code generation
> > independent of GOPATH since from
On Thu, Sep 26, 2019 at 7:36 PM Dan Kortschak wrote:
>
> I am looking at some changes we have made to make code generation
> independent of GOPATH since from the SettingGOPATH page of the wiki
> says "If no GOPATH is set, it is assumed to be $HOME/go on Unix systems
> and %USERPROFILE%\go on
I am looking at some changes we have made to make code generation
independent of GOPATH since from the SettingGOPATH page of the wiki
says "If no GOPATH is set, it is assumed to be $HOME/go on Unix systems
and %USERPROFILE%\go on Windows."
However, when I run `go env` I see `missing $GOPATH` in
