Re: The new annotation Groovydoc for Groovy 3

Very interesting Dani. Although I can think myself a couple of use cases for this, I'm intrigued, where did this come from ? What was the scenario you had in mind ? On 10 Apr 2017 02:26, "Daniel Sun" wrote: We can call it "Runtime Groovydoc". -- View this message in

Re: build requirements for Groovy and language level in master

> And then there is the matter of going to JDK8 master is supposed to be Groovy 3 did we say we want to go to JDK8 here? I think that would be nice... and of course if JDK8 is the minimum could start thinking about having indy enabled by default. Here too I would to hear what people think It

Re: The new annotation Groovydoc for Groovy 3

We can call it "Runtime Groovydoc". -- View this message in context: http://groovy.329449.n5.nabble.com/The-new-annotation-Groovydoc-for-Groovy-3-tp5739731p5739733.html Sent from the Groovy Dev mailing list archive at Nabble.com.

Re: build requirements for Groovy and language level in master

On Sat, Apr 8, 2017 at 1:11 AM, Jochen Theodorou wrote: > Hi all, > > so if we want to be serious about JDK9 support and not life with a > thousands of warnings displayed whenever you try to execute a Groovy > program or test (44k+ in our build for example)... then we will

The new annotation Groovydoc for Groovy 3

Hi all, The new annotation Groovydoc has been added in the parrot branch, it can hold groovydoc even at runtime. The usage is very simple, just add @Groovydoc at the beginning of the content of groovydoc, then the Parrot parser will attach Groovydoc annotation to the target element,

Re: Towards a better compiler

On 09.04.2017 11:53, Cédric Champeau wrote: [...] There are hundreds of places where we use hash sets/maps, with objects that do not implement equals/hashcode, for example (and since those structures are mutable, we're very lucky because the default hashcode uses the system one, which is

Towards a better compiler

Hi team! I would like to setup some additional goals for the next release of Groovy. As you may know, Gradle 3.5, released tomorrow, will ship with a build cache [1]. But Groovy is causing us some troubles, because the output of compilation is not reproducible. In other words, for the same

Re: build requirements for Groovy and language level in master

On April 8, 2017 7:35:18 PM GMT+02:00, Jochen Theodorou wrote: >On 08.04.2017 16:29, Remi Forax wrote: >> Jochen, >> technically, you do not need the jdk 9, >> you can compile with jdk 8 and have a jar that contains the >declaration >> of methods of the jdk 9 you want. >