If anyone involved in android support is reading this, could they please
review https://github.com/apache/groovy/pull/648 ? I'd like to get that in
2.5.
On Tue, Feb 6, 2018 at 10:25 AM, wrote:
> Daniel,
> Could you please wait? Each time Paul has announced 2.4
>
> In addition, the following issue[4] should be fixed too. I think I have
> not found a correct way to use ClassNode instance, any help is appreciated!
> ```
> A transform used a generics containing ClassNode Test1 for the method
> public
> static int doCall(Test1 __this, java.lang.Integer e) {
Nice!
On Thu, Dec 21, 2017 at 8:45 AM, Daniel.Sun wrote:
> Thanks ;-)
>
>
>
> --
> Sent from: http://groovy.329449.n5.nabble.com/Groovy-Dev-f372993.html
>
Perhaps it falls into an abuse of exceptions for control flow, but that
would make sense when variable 'a' is not necessarily defined, but if it
is, its member 'b' should be present.
I am also opposed to the new syntaxes outside of !instanceof, !In, and ?=
for assignments.
On Thu, Oct 5, 2017 at
Congratulations John!
On Sun, Apr 2, 2017 at 8:35 AM Cédric Champeau
wrote:
> Congrats and welcome, John!
>
> 2017-04-02 12:49 GMT+02:00 jim northrop :
>
> Welcome aboard John!
>
> Sent from my iPad
>
> > On 2 Apr 2017, at 11:11,
Congratulations, and welcome! Looking forward to playing with the macro
system in depth one of these weekends.
On Sat, Dec 10, 2016 at 10:36 PM, Keegan Witt wrote:
> Congrats Sergei, and welcome!
>
> -Keegan
>
> On Sat, Dec 10, 2016 at 12:47 PM, John Wagenleitner <
>
>
> while I agree that ||= is more like what ruby offers we have the problem,
> that for Groovy a||b always will be evaluated as boolean.
> In fact first we apply groovy truth to a and if that is not true, we do
> the same for b and if that is not true we return false, otherwise true.
> Which
+1 I was writing a type checking extension that did this but it would much
better if it were built into the compiler itself
On Tue, Oct 4, 2016 at 11:18 AM, Jochen Theodorou wrote:
> sounds good
>
>
> On 04.10.2016 14:56, Graeme Rocher wrote:
>
>> Hi all,
>>
>> I would like
The annotationNodes list for an AnnotatedNode is accessible and and mutable
so you should be able to remove it yourself.
On Wed, Apr 20, 2016 at 7:56 AM, Mario Garcia wrote:
> I don't know how to do this. Looking the g/api there is a "addAnnotation"
> but there is not a