You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After upgrading to Java 7, I was curious to see if it would have any performance impact on the places where I use structural dispatch in my project. I guess ClassNotFoundException pops up pretty quickly, but it wasn't exactly what I was hoping for.... :-)
It seems that the -Ystruct-dispatch:invoke-dynamic option is still based on an early version of the JSR, when the code still lived in java.dyn. It has since been refactored a bit and transitioned into java.lang.invoke.
Easily worked around by going back to cached dispatch.
The text was updated successfully, but these errors were encountered:
Sarah Gerweck (gerweck) said:
I'm not suggesting that this work should be urgent, but it might make sense to disable the option if it's easy. I know -Y options generally fall in the "at your own risk" category but I'd hate for somebody to turn this on and have the issue slip past their testing.
After upgrading to Java 7, I was curious to see if it would have any performance impact on the places where I use structural dispatch in my project. I guess
ClassNotFoundException
pops up pretty quickly, but it wasn't exactly what I was hoping for.... :-)It seems that the
-Ystruct-dispatch:invoke-dynamic
option is still based on an early version of the JSR, when the code still lived injava.dyn
. It has since been refactored a bit and transitioned intojava.lang.invoke
.Easily worked around by going back to cached dispatch.
The text was updated successfully, but these errors were encountered: