One way for them to be "imported by default" would be to move them to the
groovy.lang package. I'd make sure ClosureParams and DelegatesTo come along
for the ride if such a change is made.
From: Daniel.Sun
Sent: Sunday, October 27, 2019 9:39 PM
To: d...@groovy.i
Interestingly, historically, we've gone the other way round, to move
default-imported transforms in non-default-imported packages,
like @Delegate, and others.
Also for those who frequently use these transformations, there's also the
option of defining a compiler configuration script that can be pas
I agree, my general opinion is that there is already the config script
mechanism to either 1) add imports, 2) add star imports or 3) enable specific
AST transforms without the need for annotating sources.
There was a change a few months back to try and enable static compilation by
default and i
Greoovy 3.0, yes, but surely there will be a Groovy 3.1 ?-)
On 28/10/2019 03:39, Daniel.Sun wrote:
Hi mg,
Groovy 3 is already in RC phase, so its features are frozen. New
features are targeted to next version.
Cheers,
Daniel.Sun
-
Apache Groovy committer & PMC member
Blog: http:/
Config script is for Groovy power users. I think the idea behind this
feature would be to enable everyone to use these often used annotations
without any hassle in a Groovy script (IDEs will insert the import
automatically anyway), as to encourage their use.
Enabling static compilation by defa
