Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
cmd/go: build: add -buildmode=nolink flag #31710
My understanding of the "go build" process is it does something like this:
It builds the "errors" package because vim-go desperately does not want to build any final artifacts, and attempting to build multiple packages turns off the binary building behavior.
However, I notice that this never takes advantage of build caching. That is, if I run
Is there a way to make "go build" take advantage of whatever intermediate build steps exist - the
Alternatively, can you work with the
referenced this issue
Apr 27, 2019
This is taking advantage of build caching.