With module aware go the GOPATH semantics are gone, replaced with a separate root source tree approach.
I was using Goland pointing at GOPATH and thus any 'go get' would add a package to my environment and index. Also any 'go install's would show an executable in GOPATH/bin within the same environment.
With module aware go, what is the intended user story for Goland? Have each module root as a separate Goland environment?