Wish I could be there and work on macro stuff :)
On Thu, 11 Feb 2016 at 11:14 PM Guillaume Laforge
wrote:
> Hi there,
>
> Apache has submitted itself as an organization to the Google Summer of
> Code.
> Anyone Groovy committer who would be willing to become a mentor?
> And what projects would we
+1
Currently forces some really nasty workarounds because of servlet-api
conflicts when Groovy CLI is being used. As well as jsp-api
On Mon, Apr 18, 2016 at 1:19 PM daniel_sun wrote:
> +1
>
>
>
> --
> View this message in context:
> http://groovy.329449.n5.nabble.com/GROOVY-5727-removal-of-serv
Hey Mario,
Good catch! Maybe we should add it to documentation (when there will be
some :D )
BR,
Sergei
On Tue, Apr 19, 2016 at 6:21 PM Mario Garcia wrote:
> I figured out why:
>
> By default macros are using CompilePhase.CONVERSION and at this point the
> compiler doesn't care about types. T
Hey, everyone.
It's been awhile since last time I participated in Groovy.
I was mostly in read-only mode for the last two years.
With this move, I hope to change it.
I created a proposal for macro methods (no ETA, initially aimed to 3.0)
because I think they are great for the future of Groovy an
Java but in Groovy
> would apply the macro transformations.
>
>
>
> Jason
>
>
>
> *From:* Sergei Egorov [mailto:bsid...@gmail.com]
> *Sent:* Friday, September 23, 2016 5:58 AM
> *To:* dev@groovy.apache.org; us...@groovy.apache.org
> *Subject:* Macro methods propo
, and
> knows the method returns the same type as the argument, but you still have
> access to the macro context via static methods which could be implemented
> using thread locals or similar. The signature could also be used to
> restrict the type of the expression allowed, although in m
Hi all,
just curious - will it be possible to do "any statement is an expression"
with the new grammar?
That would be really awesome, especially for macro methods
BR,
Sergei
On Fri, Sep 30, 2016 at 10:31 AM daniel_sun wrote:
> Hi Jochen,
>
> The groovy grammar bases on Java7
> grammar(h
Hi Graeme,
FYI a few years ago I created an AST transformation for MapArguments:
https://github.com/bsideup/GroovyMapArguments/blob/master/src/test/groovy/ru/trylogic/groovy/mapargs/MapArgumentsTest.groovy
Might be helpful :)
BR,
Sergei
On Tue, Oct 4, 2016 at 5:33 PM Graeme Rocher
wrote:
> C
Hey Mario,
Wow! This is great! Didn't know you're working on it. I'll be happy to
review :)
Cheers,
Sergei
On Fri, Oct 7, 2016 at 1:53 PM Mario Garcia wrote:
> Hi all:
>
> I sent a WIP with some groovy-macro documentation. The main problem with
> the PR is that there're two tests failing. I'v
g. def \u9fa5 = 123
>
> At last, I want to thank* Jochen Theodorou* and *Paul King* who
> helped me confirm issues and offered suggestions, *Sergei Egorov* who
> helped
> me fix the 3 failing test cases related to MacroGroovy, *Cédric Champeau*
> who offered me a new CI instanc
How about is and !is ? Would be nice to have them :)
On Fri, Nov 18, 2016 at 4:53 PM Remi Forax wrote:
>
>
> - Mail original -
> > De: "Graeme Rocher"
> > À: dev@groovy.apache.org
> > Cc: d...@groovy.incubator.apache.org
> > Envoyé: Vendredi 18 Novembre 2016 15:16:04
> > Objet: Re: Nega
+1 for ||=
Very convenient operator, doesn't break readability (more or less)
On Tue, Nov 22, 2016 at 4:25 PM Guillaume Laforge
wrote:
> It's a feature that's often be requested.
> I think Ruby's got an equivalent with ||=, and it's often the reference
> people give when exploring our Elvis ope
Hey Jorge,
You can also take a look at:
https://github.com/bsideup/groovy-pattern-match/blob/e2c2b0472b7d078a8b299085705584cfea827405/src/test/groovy/ru/trylogic/groovy/pattern/PatternMatchingMacroMethodsTest.groovy
This is pattern matching implemented as a macro method, without touching
the syn
o)
On Fri, Sep 23, 2016 at 4:54 PM Sergei Egorov wrote:
> Unfortunately, it will not work for 100% cases.
>
> I.e. macro method accepts ConstantExpression. You can't a method in Groovy
> with such constraints.
>
> Plus, such signature doesn't make sense for IDEs as wel
https://github.com/bsideup/groovy-macro-methods-proposal
I'm looking forward to being an active committer!
Thanks,
Sergei Egorov
On Sat, Dec 10, 2016 at 11:08 AM Cédric Champeau
wrote:
> Hi folks,
>
> I'd like to introduce you to Sergei Egorov, our new Apache Groovy
> committ
Hi Daniel,
To be honest, I don't like it, -1 from me.
Why? Because we already put more and more stuff into the groovy itself,
but, i.e. in a case of python, SimpleHTTPServer it's just a module after
all.
I would rather see something like:
groovy -m com.sparkjava:spark-groovy -c "serve(port: 808
FYI https://github.com/igor-suhorukov/mvn-classloader
On Tue, Jan 10, 2017 at 11:43 AM Romain Manni-Bucau
wrote:
> Hmm, ibiblio (localm2 in grapesConfig.xml) has setChangingPattern(
> ".*-SNAPSHOT"); so should have worked OOTBbut
>
> org.apache.ivy.plugins.resolver.ChainResolver#getDependenc
-1 from me.
First of all, it's hard to understand what it does and to read it later.
Also, => is Lambda notation in JS/C# and people from these languages will
be very confused about it.
On Thu, Jan 26, 2017 at 12:06 PM Remi Forax wrote:
> The other problem i see is that the fat arrow => is used
YES from me.
Would be great if we can deliver #1 as a macro method, not it form of
"MacroGroovy" (and hopefully forget this awkward name collision :D )
Just want to remind that there is a PR waiting for a review where I rewrote
it and implemented basic macro methods support:
https://github.com/ap
Hey Andrew,
How about AstNodeToScriptVisitor? Pretty enough? :)
http://stackoverflow.com/questions/35960804/convert-ast-nodes-string-to-groovy-code/35991091#35991091
On Thu, Mar 16, 2017 at 11:40 PM Jochen Theodorou wrote:
> On 16.03.2017 17:46, Andrew Bayer wrote:
> [...]
> > I don't think t
Hi Paul,
Sounds great, thank you!
Let me know if you'll spot something to fix before the merge, will do my
best to fix it quickly.
BR,
Sergei
On Mon, Mar 27, 2017 at 4:22 PM Paul King wrote:
> Hi, I have been playing around with Sergei's latest macro methods PR
> today and it looks good to m
+1
Would be nice to test macro stuff :)
On Wed, 29 Mar 2017 at 07:18, Russel Winder wrote:
>
> > [ ] +1 Release Apache Groovy 2.5.0-alpha-1
> > [ ] 0 I don't have a strong opinion about this, but I assume it's ok
> > [ ] -1 Do not release Apache Groovy 2.5.0-alpha-1 because...
>
> Now that Git
Okay, it's a leftover in build.gradle of groovy-macro.
"org.codehaus.groovy.macro.*runtime*.MacroGroovyMethods" but should be
"org.codehaus.groovy.macro.*methods*.MacroGroovyMethods"
Also, we don't merge "org.codehaus.groovy.transform.ASTTransformation"
files when doing a jarjar-ing of groovy-all
-1
We have 1 failing test ( "MacroTest > testNotAMacroCall" )
Was caused by my recent change when I renamed extension module, sorry.
I pushed a test fix. Assumption was incorrect, see the commit for an
explanation.
On Wed, Mar 29, 2017 at 4:18 PM Paul King wrote:
> Dear community,
>
> I am hap
learn about them.
On Wed, Mar 29, 2017 at 5:16 PM Jochen Theodorou wrote:
>
>
> On 29.03.2017 17:06, Sergei Egorov wrote:
> > -1
> > We have 1 failing test ( "MacroTest > testNotAMacroCall" )
> >
> > Was caused by my recent change when I renamed extensi
Guillaume,
Yes, I fixed this test already, builds are running, locally is green as
well.
I had two long flights from 6am, please excuse me for today :)
On Wed, Mar 29, 2017 at 5:22 PM Sergei Egorov wrote:
> Jochen,
>
> This is a good question :)
>
> I'm going to present
Jdk8Build_2
On Wed, Mar 29, 2017 at 5:26 PM Guillaume Laforge
wrote:
> We have some documentation from Mario :
>
> https://github.com/apache/groovy/blob/master/src/spec/doc/core-metaprogramming.adoc#macros
>
> On Wed, Mar 29, 2017 at 5:22 PM, Sergei Egorov wrote:
>
> Joch
+1
Was using it during my macro methods workshop (thanks to https://jitpack.io/ ),
all went well :)
On Sat, Apr 1, 2017 at 12:37 AM John Wagenleitner <
john.wagenleit...@gmail.com> wrote:
> +1
>
> On Wed, Mar 29, 2017 at 10:49 PM, Paul King wrote:
>
> Dear community,
>
> I am happy to start the
28 matches
Mail list logo
