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 
Toolbar)" has 789 votes, just slightly below the front runner, "CPP-494 
Support Makefile projects" at 816 - maybe someone could tell these guys 
it's 2000 ;-) )

mg


On 21.03.2018 14:36, Daniel.Sun wrote:

Here is the link:  https://youtrack.jetbrains.com/issue/IDEA-188050

Cheers,
Daniel.Sun




--
Sent from: http://groovy.329449.n5.nabble.com/Groovy-Users-f329450.html

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 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 22 Mar 2018, at 15:42, mg  wrote:
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, default 
methods 
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 
parsers for (almost) each language.

—

Daniil Ovchinnikov
Software Developer
JetBrains
jetbrains.com
“Drive to develop”



> On 21 Mar 2018, at 22:30, mg  wrote:
> 
> I guess the Groovy 3.0/3.0-- (aka 2.6) syntax elements support will be 
> switchable in IntelliJ, anything else would make little sense to me.
> But we have the expert on this mailing list, who should be able to tell us... 
> :-)
> mg
> 
>  Ursprüngliche Nachricht 
> Von: "Daniel.Sun" 
> Datum: 21.03.18 17:10 (GMT+01:00)
> An: us...@groovy.incubator.apache.org
> Betreff: RE: Groovy 3 lambda, method reference, default methods
> 
> You can write Java8 style code(e.g. lambda, method/constructor reference,
> etc.) when Parrot parser is enabled :-)
> See https://github.com/danielsun1106/groovy-parser
> 
> 
> > Is there then a major difference in language between 2.6+Parrot and 3.0?
> 
> 3.0 enables Parrot parser by default, so no differences.
> 
> 
> > I wonder if the IntelliJ support ticket should be updated to say support
> > new language features in Groovy 2.6 as well?
> 
> I see the title contains "Groovy 3", so I am not sure if it will support 2.6
> 
> 
> Cheers,
> Daniel.Sun
> 
> 
> 
> 
> --
> Sent from: http://groovy.329449.n5.nabble.com/Groovy-Users-f329450.html

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 version).



On Thu, Mar 22, 2018 at 10:59 PM, Daniil Ovchinnikov <
daniil.ovchinni...@jetbrains.com> wrote:

> 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 22 Mar 2018, at 15:42, mg  wrote:
>
> 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, default methods
>
> 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 parsers for (almost) each language.
>
> —
>
> Daniil Ovchinnikov
> Software Developer
> JetBrains
> jetbrains.com
> “Drive to develop”
>
>
>
> > On 21 Mar 2018, at 22:30, mg  wrote:
> >
> > I guess the Groovy 3.0/3.0-- (aka 2.6) syntax elements support will be
> switchable in IntelliJ, anything else would make little sense to me.
> > But we have the expert on this mailing list, who should be able to tell
> us... :-)
> > mg
> >
> >  Ursprüngliche Nachricht 
> > Von: "Daniel.Sun" 
> > Datum: 21.03.18 17:10 (GMT+01:00)
> > An: us...@groovy.incubator.apache.org
> > Betreff: RE: Groovy 3 lambda, method reference, default methods
> >
> > You can write Java8 style code(e.g. lambda, method/constructor reference,
> > etc.) when Parrot parser is enabled :-)
> > See https://github.com/danielsun1106/groovy-parser
> >
> >
> > > Is there then a major difference in language between 2.6+Parrot and
> 3.0?
> >
> > 3.0 enables Parrot parser by default, so no differences.
> >
> >
> > > I wonder if the IntelliJ support ticket should be updated to say
> support
> > > new language features in Groovy 2.6 as well?
> >
> > I see the title contains "Groovy 3", so I am not sure if it will support
> 2.6
> >
> >
> > Cheers,
> > Daniel.Sun
> >
> >
> >
> >
> > --
> > Sent from: http://groovy.329449.n5.nabble.com/Groovy-Users-f329450.html
>
>
>

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 22 Mar 2018, at 15:42, mg  wrote:
> 
> 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, default methods
> 
> 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 
> parsers for (almost) each language.
> 
> —
> 
> Daniil Ovchinnikov
> Software Developer
> JetBrains
> jetbrains.com
> “Drive to develop”
> 
> 
> 
> > On 21 Mar 2018, at 22:30, mg  wrote:
> > 
> > I guess the Groovy 3.0/3.0-- (aka 2.6) syntax elements support will be 
> > switchable in IntelliJ, anything else would make little sense to me.
> > But we have the expert on this mailing list, who should be able to tell 
> > us... :-)
> > mg
> > 
> >  Ursprüngliche Nachricht 
> > Von: "Daniel.Sun" 
> > Datum: 21.03.18 17:10 (GMT+01:00)
> > An: us...@groovy.incubator.apache.org
> > Betreff: RE: Groovy 3 lambda, method reference, default methods
> > 
> > You can write Java8 style code(e.g. lambda, method/constructor reference,
> > etc.) when Parrot parser is enabled :-)
> > See https://github.com/danielsun1106/groovy-parser
> > 
> > 
> > > Is there then a major difference in language between 2.6+Parrot and 3.0?
> > 
> > 3.0 enables Parrot parser by default, so no differences.
> > 
> > 
> > > I wonder if the IntelliJ support ticket should be updated to say support
> > > new language features in Groovy 2.6 as well?
> > 
> > I see the title contains "Groovy 3", so I am not sure if it will support 2.6
> > 
> > 
> > Cheers,
> > Daniel.Sun
> > 
> > 
> > 
> > 
> > --
> > Sent from: http://groovy.329449.n5.nabble.com/Groovy-Users-f329450.html
>

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, default 
methods 
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 
parsers for (almost) each language.

—

Daniil Ovchinnikov
Software Developer
JetBrains
jetbrains.com
“Drive to develop”



> On 21 Mar 2018, at 22:30, mg  wrote:
> 
> I guess the Groovy 3.0/3.0-- (aka 2.6) syntax elements support will be 
> switchable in IntelliJ, anything else would make little sense to me.
> But we have the expert on this mailing list, who should be able to tell us... 
> :-)
> mg
> 
>  Ursprüngliche Nachricht 
> Von: "Daniel.Sun" 
> Datum: 21.03.18 17:10 (GMT+01:00)
> An: us...@groovy.incubator.apache.org
> Betreff: RE: Groovy 3 lambda, method reference, default methods
> 
> You can write Java8 style code(e.g. lambda, method/constructor reference,
> etc.) when Parrot parser is enabled :-)
> See https://github.com/danielsun1106/groovy-parser
> 
> 
> > Is there then a major difference in language between 2.6+Parrot and 3.0?
> 
> 3.0 enables Parrot parser by default, so no differences.
> 
> 
> > I wonder if the IntelliJ support ticket should be updated to say support
> > new language features in Groovy 2.6 as well?
> 
> I see the title contains "Groovy 3", so I am not sure if it will support 2.6
> 
> 
> Cheers,
> Daniel.Sun
> 
> 
> 
> 
> --
> Sent from: http://groovy.329449.n5.nabble.com/Groovy-Users-f329450.html

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 
parsers for (almost) each language.

—

Daniil Ovchinnikov
Software Developer
JetBrains
jetbrains.com
“Drive to develop”



> On 21 Mar 2018, at 22:30, mg  wrote:
> 
> I guess the Groovy 3.0/3.0-- (aka 2.6) syntax elements support will be 
> switchable in IntelliJ, anything else would make little sense to me.
> But we have the expert on this mailing list, who should be able to tell us... 
> :-)
> mg
> 
>  Ursprüngliche Nachricht 
> Von: "Daniel.Sun" 
> Datum: 21.03.18 17:10 (GMT+01:00)
> An: us...@groovy.incubator.apache.org
> Betreff: RE: Groovy 3 lambda, method reference, default methods
> 
> You can write Java8 style code(e.g. lambda, method/constructor reference,
> etc.) when Parrot parser is enabled :-)
> See https://github.com/danielsun1106/groovy-parser
> 
> 
> > Is there then a major difference in language between 2.6+Parrot and 3.0?
> 
> 3.0 enables Parrot parser by default, so no differences.
> 
> 
> > I wonder if the IntelliJ support ticket should be updated to say support
> > new language features in Groovy 2.6 as well?
> 
> I see the title contains "Groovy 3", so I am not sure if it will support 2.6
> 
> 
> Cheers,
> Daniel.Sun
> 
> 
> 
> 
> --
> Sent from: http://groovy.329449.n5.nabble.com/Groovy-Users-f329450.html