Hi everyone and Hi Gust, first of all, I wanted to thank you and everyone involved a lot for this awesome project!
To the point:
Say you have a method like this:
int discardAndGetX(int x) {
return this.x;
}
The getter optimization doesn't check the arity of the method and pops the integer instead of this from the stack, resulting in say an NPE.
I am not sure how to fix this without compromising the performance, but it's a real problem with legacy libraries that expose such API's for compatibility…
Hi everyone and Hi Gust, first of all, I wanted to thank you and everyone involved a lot for this awesome project!
To the point:
Say you have a method like this:
The getter optimization doesn't check the arity of the method and pops the integer instead of
this
from the stack, resulting in say an NPE.I am not sure how to fix this without compromising the performance, but it's a real problem with legacy libraries that expose such API's for compatibility…