search

ajwang / groovypptest

Automatically exported from code.google.com/p/groovypptest
0 stars 0 forks source link

get rid of doCall methods #126

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
Right now for closure we generate one or two syntetic doCall methods, which 
does nothing useful but parameter transformations. It makes life harder for 
JIT

Original issue reported on code.google.com by alex.tka...@gmail.com on 16 Feb 2010 at 7:35

GoogleCodeExporter commented 8 years ago 
be sure to leave one doCall method, since we rely on it.

Original comment by eugene.v...@gmail.com on 17 Feb 2010 at 12:59

GoogleCodeExporter commented 8 years ago

Original comment by alex.tka...@gmail.com on 21 Feb 2010 at 8:18

GoogleCodeExporter commented 8 years ago

Original comment by alex.tka...@gmail.com on 7 Apr 2010 at 9:46

GoogleCodeExporter commented 8 years ago 
I don't see a second doCall method generated. Can you give an example?

Original comment by eugene.v...@gmail.com on 26 Apr 2010 at 7:16

GoogleCodeExporter commented 8 years ago 
Runnable r = { new RuntiomeException().printStackTrace() }
r.run ()

Original comment by alex.tka...@gmail.com on 26 Apr 2010 at 9:37

GoogleCodeExporter commented 8 years ago 
OK, now I see: this is more a default parameter issue, than the closures itself.

Original comment by eugene.v...@gmail.com on 26 Apr 2010 at 10:38

GoogleCodeExporter commented 8 years ago

Original comment by alex.tka...@gmail.com on 22 Jul 2010 at 5:08