Mailing-List: contact dev-help@groovy.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@groovy.apache.org
Subject: Re: Fate of TailRecursive
To: dev@groovy.apache.org
References: <CAPhzWwYipV=am2UG64NroqYtCr_R_g6s8q6yjV0K8ATB8vsCkQ@mail.gmail.com>
 <70B06B85-5497-4CDD-860A-5F02344E8FA3@gmail.com>
 <F7131964-EF3B-46F1-AD07-76649C61E6F6@gmail.com>
From: Pascal Schumacher <pascalschumacher@gmx.net>
Message-ID: <704c39fb-f10f-8018-5123-f3971d177c3c@gmx.net>
Date: Sat, 26 Nov 2016 12:06:38 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101
 Thunderbird/45.5.0
MIME-Version: 1.0
In-Reply-To: <F7131964-EF3B-46F1-AD07-76649C61E6F6@gmail.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
archived-at: Sat, 26 Nov 2016 11:06:49 -0000

it hasn't been removed

Am 26.11.2016 um 12:04 schrieb Johannes Link:
> Unless it has been removed again it should still be in core.
>
> Von meinem iPad gesendet
>
>> Am 26.11.2016 um 11:13 schrieb Andres Almiray <aalmiray@gmail.com>:
>>
>> Didn't it get merged into Groovy core after some time living as an external download?
>>
>> Sent from my primitive Tricorder
>>
>>> On Nov 26, 2016, at 10:58 AM, Johannes Link <jl@johanneslink.net> wrote:
>>>
>>> 2016-11-26 10:12 GMT+01:00 Andres Almiray <aalmiray@gmail.com>:
>>>> This is exactly what happened with @TailRecursive. The feature proved to be good enough for 80% of the cases, for the remaining it was
>>>> either verbose or required a true syntax change. It's likely this enhanced switch will encounter the same fate.
>>> What fate did @TailRecursive encounter? Just asking as the original
>>> developer of the AST transformation ...
>>>
>>> cheers, Johannes