Wed, 14 May 2014 15:41:28 -0600
8034223: Most-specific should not have any special treatment for boxed vs. unboxed types
Summary: Rewrite most-specific logic to conform to JLS 8 15.12.2.5
Reviewed-by: vromero
1 /*
2 * @test /nodynamiccopyright/
3 * @bug 8003280
4 * @summary Add lambda tests
5 * check that that void compatibility affects overloading as expected
6 * @compile VoidCompatibility.java
7 */
8 class VoidCompatibility {
10 interface Runnable { void run(); } //1
11 interface Thunk<T> { T get(); } //2
13 void schedule(Runnable r) { }
14 void schedule(Thunk<?> t) { }
16 void test() {
17 schedule(() -> System.setProperty("done", "true")); //non-void most specific
18 schedule(() -> { System.setProperty("done", "true"); }); //1
19 schedule(() -> { return System.setProperty("done", "true"); }); //2
20 schedule(() -> System.out.println("done")); //1
21 schedule(() -> { System.out.println("done"); }); //1
22 schedule(Thread::yield); //1
23 schedule(Thread::getAllStackTraces); //non-void most specific
24 schedule(Thread::interrupted); //1 (most specific)
25 }
26 }