I’m against breaking changes and changing core concepts for so little gain.
Groovy has (x) to make x an expression. We could make that lexically scoped.
Dierk
sent from:mobile
> Am 21.03.2018 um 01:53 schrieb MG :
>
> Hi Daniel,
>
>> On 21.03.2018 01:33, Daniel Sun
Done.
Dierk
sent from:mobile
> Am 17.03.2018 um 06:52 schrieb Edgar Harutyunyan :
>
> done
>
>> On 03/16/2018 09:20 PM, MG wrote:
>> 40 votes to date - great job everyone... :-)
>> Cheers,
>> mg
>>
>>
>>> On 16.03.2018 09:18, Edd Grant wrote:
>>> Also done!
>>>
I’m all for honoring contributions to the language/ecosystem/community.
Given our logo, „Groovy Star“ comes to mind :-)
Cheers
Dierk
sent from:mobile
> Am 13.02.2018 um 12:29 schrieb Paolo Di Tommaso :
>
> It sound a nice idea also to promote the visibility of the
Union types (Sum types, really) shine when used with pattern matching and
exhaustion check.
This is not provided by this proposal.
Without that, there are already a number of ways to encode them in Groovy.
-1
Dierk
sent from:mobile
> Am 23.07.2017 um 02:13 schrieb MG :
> Thank you very much Dierk. if you could make an example, that'll be GREAT.
> thanks so much!
>
>
>
> From: Dierk König <dierk.koe...@canoo.com>
> To: users@groovy.apache.org
> Sent: Saturday, December 31, 2016 4:18 AM
> Subject: Re: GroovyFX - Custom UI w