We are implementing a custom completion provider which needs to run for multiple seconds before it can provide its elements to the result set. I already read on the forum about the issue of long-running `CompletionProvider#addCompletions` implementations:
From those posts I take it that long-running completion providers are required to invoke `ProgressManager.checkCanceled()` periodically and running the actual computation in a separate thread. This seems to have the desired effect of not freezing the UI while the results are calculated, but it prevents completion suggestions from other completion provides to be shown to the user in the meantime before our own completion provider finishes.
Is there a way to properly populate the list of completion suggestions asynchronously, i.e. let the results of other providers be displayed to the user immediately, and ours will be added at the top of the completion suggestions once our completion provider is done?