Re: [go-nuts] plugins and package main

Hopefully in 1.9 then. Created issue #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 it

Re: [go-nuts] plugins and package main

On Fri, Dec 16, 2016 at 8:32 AM, David Norton wrote: > Any chance this could make it into 1.8? No. Sorry. Ian > 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: >> >

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 > > listing all

Re: [go-nuts] plugins and package main

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 > listing all packages. Would that work? I didn't mean to imply that it is necessary to list every package in the plugin. The plugin would contain

[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