groovy-parser(Parrot)

The new parser(Parrot) can parse Groovy source code and construct the related AST, which is almost identical to the one generated by the old parser(except the corrected node position, e.g. line, column of node). Currently all features of Groovy are available. In addition, the following new features have been added:

• do-while loops; enhanced (now supporting commas) classic for loops, e.g. for(int i = 0, j = 10; i < j; i++, j--) {..})
• lambda expressions, e.g. stream.map(e -> e + 1)
• method references and constructor references
• try-with-resources, AKA ARM
• switch-expression
• sealed type
• record type
• code blocks, i.e. {..}
• Java style array initializers, e.g. new int[] {1, 2, 3}
• default methods within interfaces
• additional places for type annotations
• new operators: identity operators(===, !==), elvis assignment(?=), !in, !instanceof
• safe index, e.g. nullableVar?[1, 2]
• non-static inner class instantiation, e.g. outer.new Inner()
• runtime groovydoc, i.e. groovydoc starting with /**@; groovydoc attached to AST node as metadata

JVM system properties to control parsing:

Parrot is based on the highly optimized version of antlr4(com.tunnelvisionlabs:antlr4), which is licensed under BSD. On 20161103 Parrot was contributed to Apache Groovy, but the project will be maintained as a lab to experiment new features for Groovy. You can find it at apache/groovy.

Sample Code

• Sample code from Apache Groovy 3.0 release note

FAQ

Question(from Slack):

Can someone explain to me the importance of the Parrot compiler? Basically explain like I am 5?

Answer(by Guillaume Laforge, Project Lead of Apache Groovy):

the syntax of Groovy hasn’t evolved in a long time
the current / old parser is a bit complicated to evolve
and is using a very old version of the parsing library
so any change we’d want to make to the language (a new operator, for example) becomes very complicated
So we’ve been wanting to upgrade the underlying parser library for a while, but since the library evolved a lot, that also required a rewrite of the grammar of the language
But there’s another thing to consider
Groovy’s always been adopted by Java developers easily because of how close to the Java syntax it’s always been
so most Java programs are also valid Groovy programs
it’s been important to Groovy’s success to have this source compatibility
Java 8's been out for a while already
and we’ve been asked countless times if we’d support this or that particular syntax enhancement from Java 8
for “copy’n paste compatibility”, if you will
We decided to upgrade to a newer version of our parsing library (from v2 to v4 of Antlr)
to allow Groovy’s syntax to continue to evolve
to also support new operators and things like that
but to also support Java 8 constructs, for continued compatibility
And that’s about it