On Thursday, January 9, 2020 at 3:38:56 AM UTC-5, T L wrote:
>
> Yes, when I change the "go 1.13" directive to "go 1.14", it suggests I
> need to run 'go mod vendor' to sync.
> After the sync, it works. Thanks for the help.
>
> So if the directive is 1.13, no default "-mod=vendor" compiler flag
On Thursday, 9 January 2020 08:38:56 UTC, T L wrote:
>
> Yes, when I change the "go 1.13" directive to "go 1.14", it suggests I
> need to run 'go mod vendor' to sync.
> After the sync, it works. Thanks for the help.
>
> So if the directive is 1.13, no default "-mod=vendor" compiler flag is
> se
Yes, when I change the "go 1.13" directive to "go 1.14", it suggests I need
to run 'go mod vendor' to sync.
After the sync, it works. Thanks for the help.
So if the directive is 1.13, no default "-mod=vendor" compiler flag is set?
And not any message is suggested?
On Wednesday, January 8, 2020
works for me when tested with gp1.14beta1, are you sure your go.mod has
the "go 1.14" directive?
go's tooling currently assumes vendor is a full local copy of all code
needed to build a module
with modules the recommended way is to have your patched / unavailable
module somewhere else
and poin
