[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [jdt-dev] Introducing a slow jdt completion computer
- From: Mickael Istria <mistria@xxxxxxxxxx>
- Date: Mon, 1 Jul 2019 09:51:17 +0200
- Delivered-to: email@example.com
Currently, there is a set of limitations that basically prevent JDT Editor from being able to decently deal with "slow" content-assist processors, however high is the value they ship. You probably saw this with the Chain Completion proposal ticket: it's valuable, but because it's complex, it's sometimes slow and it triggers some too long UI Freeze and sometimes reach the internal timeout in JDT, leading to the annoying pop-up.
While several of us are working to improve that state (by introducing some non-UI Thread operations JDT could use, then make JDT completions not required to run in the UI Thread to not block users, then try to run providers in parallel for faster overall results, then try to get rid of the pop-up in favor of some more integrated UIs to better handle case of long incomplete content assist processors...), it's not an easy task to change JDT without breaking it...