Method resolution pondering

2016-08-27 Thread Paul King
I am just wondering what people's thoughts are on the different approaches different parts of Groovy take for method resolution when multiple methods are matched. Given this code: import groovy.transform.CompileStatic interface FooA {} interface FooB {} class FooAB implements FooA, FooB

Re: JDK9 and the problem of @Grab

2016-08-27 Thread Paul King
I guess I haven't looked into that part of JDK9 just yet. My first reaction would be to try to see what work would be involved with the "special handling". Keeping the existing behaviour (or close to it with perhaps a few caveats) would be ideal but has to be weighed up with the amount of work requ

Re: JDK9 and the problem of @Grab

2016-08-27 Thread Jochen Theodorou
On 27.08.2016 12:28, Paul King wrote: I guess I haven't looked into that part of JDK9 just yet. My first reaction would be to try to see what work would be involved with the "special handling". Keeping the existing behaviour (or close to it with perhaps a few caveats) would be ideal but has to be

Re: Method resolution pondering

2016-08-27 Thread Jochen Theodorou
On 27.08.2016 12:22, Paul King wrote: I am just wondering what people's thoughts are on the different approaches different parts of Groovy take for method resolution when multiple methods are matched. Given this code: import groovy.transform.CompileStatic interface FooA {} interface F