Community
Participate
Working Groups
For Juno Release we are planning to provide a call completion engine based on JDT. The vision is described here http://www.eclipse.org/recommenders/documentation/completion/ and we currently have a basic implementation in our git repository. For the release we plan to refactor large parts of the code and get it to a final and stable version.
JDT call-chain completion passed review. It will be part of 0.5. There are a few known limitations: * no proper handling of generics in method returns * templates do not insert existing parameters properly These are minor limitations that will be tracked separately.
My apologies. I closed the wrong bug.
Call completion now completely works on JDT. There are three potential bottlenecks that need to be evaluated later: * Model loading. It seems that loading the call models is very time consuming. If so, this must be improved for Juno * Fetching AST: We currently use CU.reconcile to obtain the latest AST. As Dani pointed out, this operation may block the UI. This topic needs further investigation. * AST Analysis: There is a performance benchmark missing. We may have problems is complex methods. But yet we don't know. We should consider to add some perf experiments These potential issues will be investigate for M6.
