-
Type:
Bug
-
Resolution: Fixed
-
Priority:
P4
-
Affects Version/s: None
-
Component/s: specification
The more-specific method analysis fails to acknowledge that the function types of two functional interface types being compared may be generic.
Example:
interface Foo {
<T> ArrayList<T> m();
}
interface Bar {
<E> List<E> m();
}
Presumably all checks comparing the two function types should be subject to alpha-renaming (8.4.4); and an additional check should ensure that the type parameters are equivalent.
Similar changes are necessary in 18.5.4.
Example:
interface Foo {
<T> ArrayList<T> m();
}
interface Bar {
<E> List<E> m();
}
Presumably all checks comparing the two function types should be subject to alpha-renaming (8.4.4); and an additional check should ensure that the type parameters are equivalent.
Similar changes are necessary in 18.5.4.
- relates to
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
JDK-8143576 15.12.2.5: Refine parameter equality constraint for functional most-specific test
-
- Closed
-