On 7/15/26 15:55, Paul King wrote:
AI read of your response below. It suggested a whole pile of changes
to make "on-by-default" work - I need some review time still, but it's
comments included below.
No need to hurry I think. Better do it slow and right. We cannot afford
redesigning this with every major version - not if it means new
constructs and potentially breaking changes.
My Goal would be OpenClosure as new default construct at some point.
Closure and OpenClosure can coexist, Closure wrapping OpenClosure
essentially. Maybe even with a SAM-style mechanism to autoconvert. Also
since a Closure has an OpenClosure in its core, we could move the API to
the new class. I am aware of that I suggest a major change in an
essential part of Groovy. But I am having this kind of stuff in the back
of my head for years now and finally I can let it out - thanks to AI ;)
bye Jochen
