Re: Vote for Groovy 3 support in IntelliJ :-)

2018-03-22 Thread MG
Voting for "IDEA-188050 Support for Groovy 3 syntax" has slowed down, 2^7-1 at the moment. For anyone who is interested, here are all issues sorted by # of votes: https://youtrack.jetbrains.com/issues?q=sort%20by:%20Votes%20 (Yes, evidently "IDEA-163208 Add support for MacBook Touch Bar (Magic

Re: Groovy 3 lambda, method reference, default methods

2018-03-22 Thread mg
That answers the 2.6 question, thank you Daniil :-)mg Ursprüngliche Nachricht Von: Daniil Ovchinnikov Datum: 22.03.18 13:59 (GMT+01:00) An: users@groovy.apache.org Betreff: Re: Groovy 3 lambda, method reference, default methods It will be deduced it from library with a singl

Re: Groovy 3 lambda, method reference, default methods

2018-03-22 Thread Paul King
Currently, you can switch off the Antlr parser in Groovy 3.0 by setting the antlr4 switch to false. We might deem that an implementation detail rather than a supported feature. In any case, we will likely drop that fairly soon, e.g. Groovy 3.1 (unplanned version number but assuming that's the next

Re: Groovy 3 lambda, method reference, default methods

2018-03-22 Thread Daniil Ovchinnikov
It will be deduced it from library with a single switch to use Parrot in 2.6. There is no other reason not to use library version, since Groovy can’t cross compile classes to run with old Groovy versions. — Daniil Ovchinnikov Software Developer JetBrains jetbrains.com “Drive to develop” > On

Re: Groovy 3 lambda, method reference, default methods

2018-03-22 Thread mg
Will Groovy 3.0 feature support be configurable (as for Java), or will it be deduced from Groovy libs used, ... ? Ursprüngliche Nachricht Von: Daniil Ovchinnikov Datum: 22.03.18 12:41 (GMT+01:00) An: users@groovy.apache.org Betreff: Re: Groovy 3 lambda, method reference, defa

Re: Groovy 3 lambda, method reference, default methods

2018-03-22 Thread Daniil Ovchinnikov
IntelliJ will support Groovy 3 but with own parser. - using the parser provided by Groovy library restricts support to that library version; - compiler parsers are usually non-recoverable, but in IntelliJ we want to provide ability to work with broken code as much as possible, so we have own p