Uploaded image for project: 'Groovy'
  1. Groovy
  2. GROOVY-4705 Compiler internals improvements collection task for Groovy 4
  3. GROOVY-4618

Have a transform save the AST to an external file or data structure

    XMLWordPrintableJSON

Details

    • Sub-task
    • Status: Open
    • Major
    • Resolution: Unresolved
    • None
    • None
    • Compiler
    • None

    Description

      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

      Attachments

        Activity

          People

            Unassigned Unassigned
            blackdrag Jochen Theodorou
            Votes:
            1 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated: