Summary: | More intelligent code assist | ||
---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Magnus Ihse Bursie <magnus.ihse.bursie> |
Component: | Core | Assignee: | David Audel <david_audel> |
Status: | RESOLVED WORKSFORME | QA Contact: | |
Severity: | enhancement | ||
Priority: | P3 | CC: | erich_gamma |
Version: | 2.0 | ||
Target Milestone: | 2.1 M4 | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: |
Description
Magnus Ihse Bursie
2002-02-04 09:11:01 EST
Philippe has looked into this. It would require to consider the left hand side of the assignment when computing proposals. This is doable, but it is problematic in the case of an expression like: String s= a.getString() In this case you want to get the full set of proposals on the right hand side of the expression. However, your examples below make we wonder whether the code assist engine could handle proposals after new specially. Moving to JDT Core for comment. No, this wouldn't work either. One could write: Foo myFoo = new FooFactory().getFooInstance(); The sorting is interesting, and I believe it would require an API change so as to give a different answer in the case the left-hand side type is matching the return type of the inserted completion... Need to think about it some more, but what about post 2.0 ? Deferring. Reopening Clearing resolution Hi David, I think this should be yours (related to code assist). These features are in M3(20021115) build. // String is the first proposal String s = new S<cursor> // x2 is the first proposal int x1 String x2 String s = x<cursor> // foo2 is the first proposal X foo1(){...} String foo2(){...} void bar(){ String s = foo<cursor> } Closing. |