Dug a bit further. The way our build works (debian build which copies files
into a build area) meant that 'go vet' was running on the files in 2
different locations. All worked fine in the build area, but in the source
area, it was generating the spurious 'undefined method' error. By filtering
Hmm ... obviously not as simple a problem as I first thought. I'll need to
start with the definitely failing code and reduce it to as simple a case as
possible that still exhibits the problem. Had (wrongly) assumed it would
happen in all cases hence the simple example given initially.
On
I can't reproduce the error you're seeing either in 1.15 or in later
versions with the code you provided
On Friday, August 27, 2021 at 10:11:07 AM UTC+2 wji...@gmail.com wrote:
> Hi,
>
> We've recently moved from using 'go tool vet' to 'go vet' (we need to
> stick to the Go versions shipped
