[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 10:58:01 +0200
- Delivered-to: firstname.lastname@example.org
You cannot change the JDT editor choice on that matter without subclassing the editor. You could subclass the JDT editor and try this but (additionally to the issue described above about InvalidThreadAccess) it would then be a different editor, that people would need to chose manually over JDT's one an so on.
There is no room for workarounds on this topic. It's JDT that needs to be improved; anything else will in the end result in more expensive, less reliable and less valuable work.
So if you want it remediated, I suggest you give a try to the related Platform and JDT patches already on Gerrit, and check whether they're working as expected and whether they help you -even a very small bit- in plugging you slow content assist processor.