Re: [jdt-dev] Async completions support

[Gayan Perera <gayanper@xxxxxxxxx>]

Hi all,

When we can say we support all computers to run without UIThread ? I mean at some point we need to drop the UIThread support and only support Async completions. 

We need to use the platform provided features to make JDT better and compete with other editors out there. 

Best regards,

Gayan

On Sun, 16 Aug 2020 at 23:22, Mickael Istria <mistria@xxxxxxxxxx> wrote:

Platform has support for "incremental" async content-assist, where each provider can add their content asynchronously and the pop-up updates the content when a provider completes. The generic editor enables this by default.

JDT doesn't have that, because extensibility of content assist happens downstream and all the contributors are more or less aggregated into a single provider which may require the UI Thread, so all results are returned simultaneously whenever the last content-assist extension completes.

Changing this so JDT contributes multiple providers to Platform (so updates can happen incrementally on each provider completion) might be doable, but not easy to do it right and safely IMO.

_______________________________________________

jdt-dev mailing list

jdt-dev@xxxxxxxxxxx

To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jdt-dev