You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@groovy.apache.org by "Jochen Theodorou (Jira)" <ji...@apache.org> on 2026/09/04 18:40:00 UTC
[jira] [Closed] (GROOVY-4618) Have a transform save the AST to an external file or data structure
[ https://issues.apache.org/jira/browse/GROOVY-4618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jochen Theodorou closed GROOVY-4618.
------------------------------------
Resolution: Fixed
has long be realized
> Have a transform save the AST to an external file or data structure
> -------------------------------------------------------------------
>
> Key: GROOVY-4618
> URL: https://issues.apache.org/jira/browse/GROOVY-4618
> Project: Groovy
> Issue Type: Sub-task
> Components: Compiler
> Reporter: Jochen Theodorou
> Priority: Major
>
> As of Groovy-544 we now that saving the ASt in a ClassNode is probably too much. The 64k limit was broken easily and such big class files are not good for Groovy in general.
> so the new idea is to have the class instead marked by a local transform and its ASt or the source in some format saved during compilation. For example an external file could be created... for example an additional class containing a String, that does not break the 64k limit because we split the string constant in smaller chunks. In inner class could be used for that, or other means. The details are still to be discussed here.
> But this way we can easily save the AST and reconstruct data for GROOVY-544, GROOVY-1877 or GROOVY-2450
> I close these issues in favor for this one as duplicates
--
This message was sent by Atlassian Jira
(v8.20.10#820010)