proposal: add a domain concept to make plugins unloadable.

[zigo101]

Now loaded plugins can't be unloaded. This prevents plugins being used for many situations.

Maybe load a plugin in a separated domain and destroy the domain later can solve this problem.

[crawshaw]

What is a domain?

There are a lot of problems with unloading plugins that have been discussed on other issues. Any proposal to add plugin unloading needs to address them.

An example: if I create a value of a type T that comes from a plugin, then put that value into an interface{} variable, then unload the plugin the type came from, what happens? How does the runtime implement it?

Another example: If a plugin starts a goroutine, what happens to it on unload?

Without a concrete description of the proposal, this is a feature request and not a proposal. I'm going to close it as such. If you would like to turn this into a concrete proposal addressing both the semantics of plugin unloading and how to implement it, comment and I'll reopen this.

[crawshaw]

In its current form, this is a duplicate of #20461.

[zigo101]

Ref:
http://help.adobe.com/en_US/flex/using/WS2db454920e96a9e51e63e3d11c0bf619ab-7ffc.html
http://help.adobe.com/en_US/flex/using/WS2db454920e96a9e51e63e3d11c0bf619ab-7ff2.html