groovy-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paul King (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (GROOVY-6184) Make ClassHelper consistent in how it creates ClassNodes
Date Wed, 26 Apr 2017 16:03:04 GMT

    [ https://issues.apache.org/jira/browse/GROOVY-6184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15985049#comment-15985049
] 

Paul King commented on GROOVY-6184:
-----------------------------------

This was back-ported to the 2_4_X branch, so adjusting the fix version.

> Make ClassHelper consistent in how it creates ClassNodes
> --------------------------------------------------------
>
>                 Key: GROOVY-6184
>                 URL: https://issues.apache.org/jira/browse/GROOVY-6184
>             Project: Groovy
>          Issue Type: Improvement
>          Components: Compiler
>            Reporter: Andrew Eisenberg
>            Assignee: C├ędric Champeau
>             Fix For: 2.4.11
>
>
> The ClassHelper class in almost all cases creates class nodes for its static fields using
the {{makeWithoutCaching}} method.  There are 2 exceptions: {{Annotation}} and {{Enum}}. 
My understanding is that this is a holdover from the pre-Java5 days.  The problem is that
this has huge memory ramifications on Groovy-Eclipse. So, I would like to see this changed.
> See this branch for what I am talking about:
> https://github.com/aeisenberg/groovy-core/tree/ClassHelper-ClassNode-generation



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message