groovy-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jochen Theodorou <blackd...@gmx.org>
Subject Re: Is FieldsAndPropertiesStaticCompileTest#testUseGetterFieldAccess really correct?
Date Fri, 24 Nov 2017 16:31:14 GMT


Am 24.11.2017 um 13:09 schrieb Mauro Molinari:
> I think this is a quite "grey" area of Groovy, at least it took a while 
> for me to understand getter/setter vs direct field access in different 
> cases when I faced it and some fixes to the Groovy plugin for Eclipse 
> were also necessary to properly support code highlighting and navigation.
> Now you're going further in the analysis by adding inheritance and 
> member visibility to the picture. IMHO Groovy should define a coherent 
> and consistent policy for this and proper documentation should be provided.

agreed, right now that is only halfway specified

> Just one question: when you talk about "this.x and super.x", you also 
> mean the case in which "this." is implicit, don't you?

I mean the explicit this. The implicit this is the same except for 
closure bodies and possibly inner classes

> In any case, IMHO the @CompileStatic case should behave exactly like 
> @CompileDynamic, absolutely!

Here we always have to consider how Java behaves in in how far the 
dynamic case prevents a fully static case.

bye Jochen

Mime
View raw message