Summary: | [assist] Constructor completion makes array allocation difficult | ||||||
---|---|---|---|---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Darin Wright <darin.eclipse> | ||||
Component: | Core | Assignee: | David Audel <david_audel> | ||||
Status: | VERIFIED FIXED | QA Contact: | |||||
Severity: | normal | ||||||
Priority: | P3 | CC: | daniel_megert, Olivier_Thomann | ||||
Version: | 3.5 | ||||||
Target Milestone: | 3.5 M6 | ||||||
Hardware: | PC | ||||||
OS: | Windows XP | ||||||
Whiteboard: | |||||||
Attachments: |
|
Description
Darin Wright
2009-01-29 12:24:58 EST
Right, in that case we should also see types. Moving to JDT Core. Created attachment 124690 [details]
Proposed fix
With patch types are also proposed when the expected type in an array.
eg.
X[] x = new Y|
eg.
void foo(X[] x) {
foo(new Y|
eg.
X[] foo() {
return new Y|
I can not compute types hierarchies (too costly) so i can not propose only subtypes of X.
Released for 3.5M6 Tests added CompletionTests#testConstructor1() -> testConstructor6() Verified for 3.5M6 using I20090310-0100. |