The pkg plugin is intended to allow writing "plugin-aware" Go apps, and plugins for them - cooperatively (that is, a "host" app must use this package and provide explicit "hook" points for plugins). The idea is outlined (since quite long ago) at the link mentioned by Ian L.T. earlier: https://golang.org/s/execmodes In other words, if an app author wants to enable writing plugins for his app, he/she can use pkg plugin as basic infrastructure for that.
On the other hand, from other posts by Ian in this thread it seems there are no plans for *compiler* plugins (that is, where the Go compiler specifically would provide some "hook" points into its internals, possibly by means of pkg plugin). W dniu niedziela, 18 września 2016 17:46:05 UTC+2 użytkownik Ian Byrd napisał: > > Ian, how would you comment this: https://tip.golang.org/pkg/plugin/? > > On Wed, Aug 31, 2016 at 11:00 AM, Ian Lance Taylor <ia...@golang.org >> <javascript:>> wrote: >> >>> The status is unchanged. There is no support for compiler plugins and >>> no plans for them. I make no promise that the Go compiler will ever >>> support plugins. I think an external program, along the lines of go >>> vet, is the right approach to use for additional static checking. >>> >> -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
