[go-nuts] Re: Why do plugins require a main package?

with exported functions and variables.Fxfunc SomeFunc() {}* > *https://golang.org/ref/spec#Exported_identifiers > <https://golang.org/ref/spec#Exported_identifiers>* > > > Den onsdag den 30. november 2016 kl. 20.13.10 UTC+1 skrev Craig Peterson: >> >> From the 1.8 plugi

Re: [go-nuts] Why do plugins require a main package?

> > > We could arrange for the go tool (probably not the compiler itself) to > optionally auto-generate a main package. Want to write a patch? > > Yes. Yes I do. Not sure exactly where to start, but I will start digging. I will file an issue to track I suppose. -- You received this message

[go-nuts] Why do plugins require a main package?

>From the 1.8 plugin docs : A plugin is a Go main package with exported functions and variables This creates a bit of a headache for me. My current setup is that a plugin is a simple library package like so: package someLibrary import "gihub.com/someapp/pl