mirror of https://github.com/golang/go.git
b894a3290f
Build flags, -mod, and -modfile are all accepted by disjoint go command verbs. Mixing them together had the effect of forcing gocommand users to figure out which went where themselves, which was annoying and error-prone. Add ModFlag and ModFile fields to Invocation and update all uses to use them. go/packages has a BuildFlags field that's bad for the same reason. Add private modFlag and modFile fields that forward to the corresponding Invocation fields. imports.ProcessEnv gets the same treatment. Fixes golang/go#41826. Change-Id: If74d19146e9e62930d7c34f40859c27c25566c4e Reviewed-on: https://go-review.googlesource.com/c/tools/+/263213 Trust: Heschi Kreinick <heschi@google.com> Run-TryBot: Heschi Kreinick <heschi@google.com> gopls-CI: kokoro <noreply+kokoro@google.com> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Rebecca Stambler <rstambler@golang.org> |
||
|---|---|---|
| .. | ||
| analysis | ||
| ast | ||
| buildutil | ||
| callgraph | ||
| cfg | ||
| expect | ||
| gccgoexportdata | ||
| gcexportdata | ||
| internal | ||
| loader | ||
| packages | ||
| pointer | ||
| ssa | ||
| types | ||
| vcs | ||