Summary: | [1.5][compiler] Inheritance with generic parameter poses problem if formulated differently | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Volker Renneberg <volker.renneberg.external> | ||||||
Component: | Core | Assignee: | JDT-Core-Inbox <jdt-core-inbox> | ||||||
Status: | RESOLVED INVALID | QA Contact: | |||||||
Severity: | normal | ||||||||
Priority: | P3 | ||||||||
Version: | 3.2 | ||||||||
Target Milestone: | 3.3 M1 | ||||||||
Hardware: | PC | ||||||||
OS: | Windows XP | ||||||||
Whiteboard: | |||||||||
Attachments: |
|
Description
Volker Renneberg
2006-06-28 05:09:10 EDT
Created attachment 45450 [details]
SuperInterface
The given interface is in a package called "inheritance".
Created attachment 45451 [details]
ProblemClass
The given interface is in a package called "inheritance".
This is the intended behavior. Javac 1.6b88 agrees with us. Now I agree on the surface this is questionnable as a wildcard is usually considered to act as a type parameter when only referenced once... To avoid the problem, define instead the following, which will be somewhat equivalent. class ProblemClass implements SuperInterface { public <B extends JLabel> void doIt(Collection<B> as) { } } Added MethodVerifyTest#test095-096 Actually, tests are MethodVerifyTest#test096-097 |