Summary: | [1.5] inconsistent compiler behavior in generic methods | ||
---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Adam Kiezun <akiezun> |
Component: | Core | Assignee: | Philipe Mulet <philippe_mulet> |
Status: | VERIFIED FIXED | QA Contact: | |
Severity: | normal | ||
Priority: | P3 | ||
Version: | 3.1 | ||
Target Milestone: | 3.1.1 | ||
Hardware: | PC | ||
OS: | Windows XP | ||
Whiteboard: |
Description
Adam Kiezun
2005-07-21 09:59:08 EDT
Agree it looks strange. Now the rules for conditional operator have been changed with 1.5 to infer most common supertype; which seems to yield Object. Interestingly, javac agrees with us. just checked, it's a bug in javac too: http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=5042462 Problem comes from that our LUB computation is performing erasure of supertypes, thus getting rid of type parameters. Added GenericTypeTest#test791 Fixed Verified for 3.2M1 (I20050808-2000) Verified using M20050923-1430 for 3.1.1 |