Jochen, lambda expression is fully supported now :)
https://github.com/danielsun1106/groovy-parser/commit/c380e4230ecef350855b9f56a220411635a7ff87
https://github.com/danielsun1106/groovy-parser/blob/master/src/test/resources/core/Lambda_01x.groovy
Cheers,
Daniel.Sun
在 "Jochen Theodorou [via
hah, I knew you can do it ;)
On 18.10.2016 18:34, daniel_sun wrote:
Jochen, lambda expression is fully supported now :)
https://github.com/danielsun1106/groovy-parser/commit/c380e4230ecef350855b9f56a220411635a7ff87
https://github.com/danielsun1106/groovy-parser/blob/master/src/test/resources/
Is it actually Groovy closures? or "real" Java lambdas?
On Tue, Oct 18, 2016 at 7:42 PM, Jochen Theodorou wrote:
>
> hah, I knew you can do it ;)
>
> On 18.10.2016 18:34, daniel_sun wrote:
>
>> Jochen, lambda expression is fully supported now :)
>>
>> https://github.com/danielsun1106/groovy-pars
I would say Groovy Closure with the Java syntax.
Rémi
On October 18, 2016 8:21:34 PM GMT+02:00, Guillaume Laforge
wrote:
>Is it actually Groovy closures? or "real" Java lambdas?
>
>On Tue, Oct 18, 2016 at 7:42 PM, Jochen Theodorou
>wrote:
>
>>
>> hah, I knew you can do it ;)
>>
>> On 18.10.20
I assumed so, but wanted to be sure :-)
On Tue, Oct 18, 2016 at 10:35 PM, Remi Forax wrote:
> I would say Groovy Closure with the Java syntax.
>
> Rémi
>
> On October 18, 2016 8:21:34 PM GMT+02:00, Guillaume Laforge <
> glafo...@gmail.com> wrote:
>>
>> Is it actually Groovy closures? or "real" J
"Real lambdas" with the full invokedynamic treatment is a big job, and requires
static type inference.
Given that Groovy can already coerce closures into functional interfaces
(dynamically), we could implement the whole metafactory-stuff with the static
compilation, and as a separate effort, rig
On Tue, Oct 18, 2016 at 4:15 PM, Jesper Steen Møller
wrote:
> "Real lambdas" with the full invokedynamic treatment is a big job, and
> requires static type inference.
> Given that Groovy can already coerce closures into functional interfaces
> (dynamically), we could implement the whole metafactor
Currently it leverages the power of closure, i.e. lambda expression for groovy
is a subclass of closure.
Cheers,
Daniel.Sun
在 "Guillaume Laforge [via Groovy]"
，2016年10月19日 上午2:21写道：
Is it actually Groovy closures? or "real" Java lambdas?
On Tue, Oct 18, 2016 at 7:42 PM, Jochen Theodorou <[h
To be exact, lambda expression of Groovy enhances the syntax of Java lambda
expression, e.g. lambda expression of Java is not callable.
Cheers,
Daniel.Sun
在 "Remi Forax [via Groovy]"
，2016年10月19日 上午4:36写道：
I would say Groovy Closure with the Java syntax.
Rémi
On October 18, 2016 8:21:34 P
Thanks for the explanations!
(and great achievement!)
On Wed, Oct 19, 2016 at 1:43 AM, daniel_sun wrote:
> To be exact, lambda expression of Groovy enhances the syntax of Java
> lambda expression, e.g. lambda expression of Java is not callable.
>
> Cheers,
> Daniel.Sun
>
>
>
> 在 "Remi Forax [vi
It is really a big job to implement the real lambda in the backend. So far so
good ;) Thank you, Jesper.
Cheers,
Daniel.Sun
在 Jesper Steen Møller [via Groovy]
，2016年10月19日 上午7:16写道：
"Real lambdas" with the full invokedynamic treatment is a big job, and requires
static type inference.
Given
Thanks :)
Cheers,
Daniel.Sun
在 "Roman Shaposhnik-2 [via Groovy]"
，2016年10月19日 上午7:17写道：
On Tue, Oct 18, 2016 at 4:15 PM, Jesper Steen Møller
<[hidden email]> wrote:
> "Real lambdas" with the full invokedynamic treatment is a big job, and
> requires static type inference.
> Given that Groovy c
Thanks :)
Guillaume, is there a road map to show us the plan of Groovy3? e.g. when to
release the first beta version and what feature should be included?
Cheers,
Daniel.Sun
在 "Guillaume Laforge [via Groovy]"
，2016年10月19日 上午7:47写道：
Thanks for the explanations!
(and great achievement!)
On Wed
Nothing's definitive at all for Groovy 2.5 or 3.0.
It's up for discussion here on the list :-)
On Wed, Oct 19, 2016 at 2:33 AM, daniel_sun wrote:
> Thanks :)
> Guillaume, is there a road map to show us the plan of Groovy3? e.g. when
> to release the first beta version and what feature should be
The new parser is based on Java8, so it has to target to Groovy3. As far I
know, there are some amazing features under development or test, e.g. MOP2, new
Joint compiler, Macro(appears at the snapshot of 2.5.0), etc. Looking forward
to them :)
Cheers,
Daniel.Sun
在 "Guillaume Laforge [via Gro
On 19.10.2016 02:49, daniel_sun wrote:
The new parser is based on Java8, so it has to target to Groovy3. As far
I know, there are some amazing features under development or test, e.g.
MOP2, new Joint compiler, Macro(appears at the snapshot of 2.5.0), etc.
Looking forward to them :)
(a) I think
(a) That's great! We can get feedback from Groovy developers and refine the new
parser.
(b) It's really a hard work. I believe you can achieve it at last :)
Cheers,
Daniel.Sun
在 "Jochen Theodorou [via Groovy]"
，2016年10月19日 上午9:30写道：
On 19.10.2016 02:49, daniel_sun wrote:
> The new parser is
17 matches
Mail list logo
