Slightly concerned about the lack of explicit option persister loading unless you now know that it's being triggered by somewhere else. But keeping it explicit would still be good I think.

What does the explicit persister loading accomplish? It's loading in a fire and forget task on a background thread and there is no guarantee that other Roslyn code using options won't run before the explicit loading.

Slightly concerned about the lack of explicit option persister loading unless you now know that it's being triggered by somewhere else. But keeping it explicit would still be good I think.

What does the explicit persister loading accomplish? It's loading in a fire and forget task on a background thread and there is no guarantee that other Roslyn code using options won't run before the explicit loading.

Was the intention a best effort (w/o guarantee) to move loading assemblies off of UI thread, in case someone accesses the option service for the first time on UI thread?

@jasonmalinowski Reverted removal of option providers pre-loading to lower risk.