HI Dain,
I would suggest using byte code for everything that byte code and falling
back to invoke dynamic only if there is no alternative.
- AJ
On 27 May 2012 19:12, Dain Sundstrom d...@iq80.com wrote:
Hi all,
I have a general strategy question about using invoke dynamic. Say I have
a
This isn't a bad rule of thumb, but I'd add a caveat:
* If you know one concrete shape will always fit the execution, emit
the bytecode IFF it's of a reasonable size
Because method handles can blur the lines between methods and dodge
some JVM inlining/optimization thresholds, they're often
My rule of thumb is: if you know that one concrete code shape will
always fit the execution, I'd just emit the bytecode. Invokedynamic is
great for cases where the executed code needs to change from time to
time. You can also combine it - the invocation of actual property
getters getA(), getB()
Hi Dain
This sounds similar to a non local return in smalltalk where some method
in a chain returns to the
starting method. I did this with a throw and a catch based on the invoker
of the chain. Seems to
work for me but I will leave it to the experts to tell you the best way
for your
Hi all,
I have a general strategy question about using invoke dynamic. Say I have a
dynamic language that has null safe property chaining where a.b.c.d results
in null if a null is encountered anywhere in the chain. I could implement this
two ways, 1) generate byte code that checks for nulls
