I wouldn't do that, extensions should just behave correctly.

OK. Indeed I don't want this to be necessary, but if it's there for safety people will start relying on it (and rightfully so, otherwise it's just dead code, right?)

And if the plugin is unloaded and the extension is still registered, there will probably be a huge crash that the extension developer notices

Most extension developers don't actually manually unload their plugin at runtime; and it's unlikely to actually cause an issue when shutting down. It's the kind of things that get noticed by random users that disable a plugin.

(not sure what happens with resident plugins in this case which the LSP plugin is).

That'll depend on the plugin, if it clears required data and doesn't guard against that, it'll probably crash. Resident modules just don't unload the code and such, but they are still getting asked to cleanup.

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.