Plugin package and Go 1 compatibility promise

[Florin Pățan]

Hi,

I would like to ask what's the status of the plugin package and if it's covered by the Go 1 compatiblity promise.

Do you think having a page in the documentation to display all the packages and their status would be something that would also solve this problem for others in the future?

Thank you.

Kind regards,

Florin

[Ian Lance Taylor]

On Thu, Aug 10, 2017 at 12:41 PM, Florin Pățan <flori...@gmail.com> wrote:
>
> I would like to ask what's the status of the plugin package and if it's
> covered by the Go 1 compatiblity promise.
> Do you think having a page in the documentation to display all the packages
> and their status would be something that would also solve this problem for
> others in the future?

The plugin package is covered by the Go 1 compatibility guarantee.
That is true in general for all the packages in the standard library.
There are a very small number of exceptions, such as
testing.MainStart, that are called out explicitly in their docs. It
might be useful to gather all the exceptions together in one place,
but it doesn't sound too important to me.

If what you are trying to get at is that the plugin package isn't
reliable, that is unfortunate but true. Still, its current
functionality is covered by the Go 1 guarantee and there is no
exception that programs that work today will stop working in the
future.

Ian