d4d5f60edc
More precise rethrow analysis should be extended to effectively-final exception parameters. Multicatch parameters should be made implicitly final. Reviewed-by: jjg, darcy
34 lines
701 B
Java
34 lines
701 B
Java
/*
|
|
* @test /nodynamiccopyright/
|
|
* @bug 6943289
|
|
*
|
|
* @summary Project Coin: Improved Exception Handling for Java (aka 'multicatch')
|
|
* @author mcimadamore
|
|
* @compile/fail/ref=Neg05.out -XDrawDiagnostics Neg05.java
|
|
*
|
|
*/
|
|
|
|
class Neg02 {
|
|
|
|
static class Foo<X> {
|
|
Foo(X x) {}
|
|
}
|
|
|
|
static interface Base<X> {}
|
|
static class A extends Exception implements Base<String> {}
|
|
static class B extends Exception implements Base<Integer> {}
|
|
|
|
void m() {
|
|
try {
|
|
if (true) {
|
|
throw new A();
|
|
}
|
|
else {
|
|
throw new B();
|
|
}
|
|
} catch (A | B ex) {
|
|
Foo<?> f = new Foo<>(ex);
|
|
}
|
|
}
|
|
}
|