On 29.03.24 21:10, Caleb Brandt wrote:
Hey all,
I'm very grateful for your feedback, and it's clear that you aren't
convinced that this will be helpful enough to be an Apache-sponsored
project.
What do you understand under "Apache-sponsored"? I do for example use
Project Lombok if I have the chance to do so and it has to be in Java. I
think many here would. The things people have been pointing out are that
you probably underestimate some of the problems and that there can be
really silly reasons to reject something.
I would for one not speak of that as a language, but just as a tool. And
next you need good integration. It must be easy to use from an IDE and
in a build... at least potentially.
I can see how you could make the build variant a GSOC project. But under
the Apache Groovy flag? I mean there is no advantage for Groovy we would
get out of this. Right now it is mostly unrelated.
If you wanted to make this a transform and with this a compiler
extension, then this is a whole different matter. It would then be at
least related to Groovy. But is there a path forward from this?
Just why to explain why I mention transforms... they are annotation
based pre-processors to some extend, just on the AST level instead the
source level. Unlike in Java transforms are allowed to mutate the
classes in almost any way.
bye Jochen
