Re: About the callable native lambda

Am 01.02.2018 um 12:50 schrieb Jesper Steen Møller: [...] class R implements Runnable { void run(){}} def m(Runnable r1, R r2, r3) { r1() r2() r3() } m(new R(), new R(), new R()) Currently, in the 'native-lambda' branch, r1() succeeds, whereas the latter two fail to

Re: About the callable native lambda

Hi again > On 1 Feb 2018, at 13.48, Jochen Theodorou wrote: > > [...] >> For static compilation, r1() and r2() should work IMHO, and r3() should be >> rejected. This shouldn't surprise anyone, I think. > > you mean because the m has a return value and r3() is void? That is

Re: About the callable native lambda

(Sorry, first version went out too soon, thanks to the silly, silly Touch Bar) > On 31 Jan 2018, at 23.01, MG wrote: > > Hi Jesper, > > seen from a Groovy user perspective your proposal seems to make sense to me. > (I would at the same time hope you do not dent Daniel Sun's