Mailing-List: contact users-help@groovy.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@groovy.apache.org
MIME-Version: 1.0
Message-ID: 
 <trinity-1c1caaa4-bdbe-4981-bd23-cf1deec4b7da-1449561429954@3capp-gmx-bs40>
From: "Jochen Theodorou" <blackdrag@gmx.org>
To: users@groovy.apache.org
Subject: Aw: CompileStatic closure accessing "this object" private variable
 via setGroovyObjectProperty
Content-Type: text/plain; charset=UTF-8
Date: Tue, 8 Dec 2015 08:57:10 +0100
Importance: normal
Sensitivity: Normal
In-Reply-To: <5C676E6359909E478C7B811BDB48CA35433FB4@CWWAPP478.windstream.com>
References: <5C676E6359909E478C7B811BDB48CA35433FB4@CWWAPP478.windstream.com>
Content-Transfer-Encoding: quoted-printable


Gesendet:=C2=A0Montag, 07=2E Dezember 2015 um 18:12 Uhr
Von:=C2=A0"Winnebeck, Jason" <Jason=2EWinnebeck@windstream=2Ecom>
An:=C2=A0"users@groovy=2Eapache=2Eorg" <users@groovy=2Eapache=2Eorg>
Betreff:=C2=A0CompileStatic closure accessing "this object" private variab=
le via setGroovyObjectProperty

I have code with performance issues using closures accessing private field=
s:
=C2=A0
@CompileStatic
class X {
=C2=A0 private Y a,b,c
=C2=A0
=C2=A0 void blah() {
=C2=A0=C2=A0=C2=A0 doClosureThing { //This gets run in a loop, 1000s of ti=
mes
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 a =3D =E2=80=A6
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 b =3D =E2=80=A6
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 c =3D =E2=80=A6
}}}
=C2=A0
When profiling, I see the majority of time is spent in ScriptBytecodeAdapt=
er=2EsetGroovyObjectProperty=2E
[=2E=2E=2E]
Is this expected behavior for static compiler?
=C2=A0

Since the compiler checks the assignments to a/b/c, it should also create =
a direct access to the variables imho=2E So my answer would be no

bye Jochen