Summary: | [1.5][compiler]Internal compiler error in org.eclipse.jdt.internal.compiler.lookup.ReferenceBinding | ||||||
---|---|---|---|---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Victor Toni <victor.toni> | ||||
Component: | Core | Assignee: | Philipe Mulet <philippe_mulet> | ||||
Status: | VERIFIED FIXED | QA Contact: | |||||
Severity: | normal | ||||||
Priority: | P3 | ||||||
Version: | 3.1 | ||||||
Target Milestone: | 3.1 M4 | ||||||
Hardware: | PC | ||||||
OS: | Windows XP | ||||||
Whiteboard: | |||||||
Attachments: |
|
Description
Victor Toni
2004-11-16 05:04:17 EST
Created attachment 15888 [details]
Stacktrace of exception
Looking at the code, it seems that TypeBinding compatible in line 658 may be null (because findSuperTypeErasingTo may return null), which is not checked in line 660. Do you have steps to reproduce ? Reproduced: public class X<T> { String foo() { return new X(); } } In theory, #needsUncheckedConversion is supposed to be invoked with compatible types, and for return type, this may not be the case. Changed return type handling, also added null check in #needsUncheckedConversion just to be sure. Added regression test: GenericTypeTest#test422. Fixed Verified in 200412140800 |