The first case being treated as an error simplifies things greatly - I
wasn't sure if that behavior was by design and I missed it or a case
we never fully fleshed out. I will create a Jira.
Paul.
On Mon, Aug 29, 2016 at 4:30 AM, John Wagenleitner
wrote:
> On Sat, Aug 27, 2016 at 4:22 AM, Joche
On Sat, Aug 27, 2016 at 4:22 AM, Jochen Theodorou wrote:
> 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:
>>
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
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
