groovy-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Daniel Sun <>
Subject 答复: Lambda vs. Closure
Date Tue, 07 Feb 2017 17:00:51 GMT
Hi Jochen,

Gotcha 😊
BTW, Generating the real lambda needs type information which is only available in the static
compilation mode…so it’s impossible to have universal version of lambda if we want to
implement the real lambda.


发件人: Jochen Theodorou [via Groovy]<>
发送时间: 2017年2月8日 0:53
收件人: Daniel Sun<>
主题: Re: Lambda vs. Closure

On 07.02.2017 16:44, Jesper Steen Møller wrote:
> Generating faster/tighter code for lambdas (or even closures) can be
> implemented as a separate task, the two aren't really interconnected,
> since the Groovy closure is so versatile to begin with.

The problem is that Closure has delegates, owners and several other
things, that make no sense for lambdas in the sense of Java. In other
words: Closure does too much and is too heavy weight

bye Jochen

If you reply to this email, your message will be added to the discussion below:
To unsubscribe from [VOTE] Apache Groovy Roadmap, click here<>.

View this message in context:
Sent from the Groovy Dev mailing list archive at
View raw message