Re: [go-nuts] plugins and package main

Hopefully in 1.9 then. Created issue #18350 <https://github.com/golang/go/issues/18350>. Thanks, Ian. On Friday, December 16, 2016 at 12:07:33 PM UTC-5, Ian Lance Taylor wrote: > > On Fri, Dec 16, 2016 at 8:32 AM, David Norton > wrote: > > Any chance this could make

Re: [go-nuts] plugins and package main

Any chance this could make it into 1.8? On Friday, December 16, 2016 at 11:24:26 AM UTC-5, Ian Lance Taylor wrote: > > On Fri, Dec 16, 2016 at 8:15 AM, David Norton > wrote: > > Or, maybe tell the go tool which package to consider "main" instead of > > listin

Re: [go-nuts] plugins and package main

Or, maybe tell the go tool which package to consider "main" instead of listing all packages. Would that work? On Friday, December 16, 2016 at 11:12:09 AM UTC-5, Ian Lance Taylor wrote: > > On Fri, Dec 16, 2016 at 8:09 AM, David Norton > wrote: > > We're exp

[go-nuts] plugins and package main

We're experimenting with the new plugin package (in go 1.8 beta) in telegraf . It would be convenient if plugin code could be in any package and not required to be in "package main". Is that possible? For example, if we wanted a package to allow both the

Re: [go-nuts] "plugin was built with a different version..."

aylor > wrote: > > [ +crawshaw ] > > > > On Wed, Dec 14, 2016 at 9:03 AM, David Norton > wrote: > >> I'm trying to better understand how the runtime checks package versions > when > >> using the plugin pkg. If there's a mismatch, the follo

[go-nuts] "plugin was built with a different version..."

I'm trying to better understand how the runtime checks package versions when using the plugin pkg. If there's a mismatch, the following error occurs at run time: plugin.Open: plugin was built with a different version of package ... > That message originates, in the runtime, here