[go-nuts] Problems with Golang plugins in Go 1.19 (versus Go 1.15)

Hi, Wondering if anyone can help me with a golang plugin problem. Apologies for not being able to provide a simple reproduction - the problem is all bound up in the Debian (dh-golang) build system. Anyway, our product is based on Debian. We have code using plugins that has been working fine with

[go-nuts] 'go vet' not finding methods exported in _test.go files?

Hi, We've recently moved from using 'go tool vet' to 'go vet' (we need to stick to the Go versions shipped with Debian) and have found that it is not finding public methods that we export for test only by putting them in _test.go files (error is 'undeclared name'). Disable go vet, and you can

[go-nuts] Re: Seeing 'plugin built with different version' errors with Go1.11 (but not with Go1.10)

of the plugin. Using trimpath / all flags is a workaround, but no more than that. Regards, William On Thursday, 5 September 2019 17:48:01 UTC+1, William Ivory wrote: > > Hi, > > I've been using Go plugins with Go1.10, and after initial problems getting > our build system to build using

[go-nuts] Seeing 'plugin built with different version' errors with Go1.11 (but not with Go1.10)

Hi, I've been using Go plugins with Go1.10, and after initial problems getting our build system to build using identical paths to avoid the dreaded 'plugin was built with a different version of package' error, it all settled down and was working well for 6 months or so. We're now trying to