-
Bug
-
Resolution: Fixed
-
P4
-
8
-
b12
At present javac don't fire a potentially ambiguous warning in the following cases:
interface I {
void foo(Consumer<Integer> c);
}
interface J {
void foo(IntConsumer c);
}
interface K extends I, J { }
--
interface I<T> {
void foo(Consumer<Integer> c);
void foo(T c);
}
interface J extends I<IntConsumer> { }
The current implementation should be improved to cover these cases too.
Consider implementing a combo test to check the scheme implementation.
interface I {
void foo(Consumer<Integer> c);
}
interface J {
void foo(IntConsumer c);
}
interface K extends I, J { }
--
interface I<T> {
void foo(Consumer<Integer> c);
void foo(T c);
}
interface J extends I<IntConsumer> { }
The current implementation should be improved to cover these cases too.
Consider implementing a combo test to check the scheme implementation.
- csr for
-
JDK-8303170 Generate "potentially ambiguous overload" for two inherited methods
- Closed
There are no Sub-Tasks for this issue.