groovy-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alain Stalder <>
Subject Re: Improve Groovy class loading performance and memory management
Date Mon, 16 May 2016 11:37:09 GMT
Ah, I think now I am getting it... In order to cache ClassInfo you need 
a key that identifies the class...

On 16.05.16 12:46, Alain Stalder wrote:
> My argument is still the same: ClassInfo (or other assiociated 
> metadata) only makes sense if you have your hands on a class (or an 
> instance of it) to apply it to. The one who wants to do something with 
> the class/instance has it and in principle can pass it down to 
> ClassInfo in order to extract whatever is needed. If there is no 
> "client" with a class/instance, there is no need to create ClassInfo 
> (or similar). And if the class is garbage collected, automatically 
> ClassInfo cannot be accessed with such queries any more, and then also 
> the JVM bug with ClassValue would no longer affect Groovy, ClassValue 
> could be used again by default. 

View raw message