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
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:
intdiscardAndGetX(intx) {
returnthis.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…
The text was updated successfully, but these errors were encountered:
I-asked
changed the title
Getter/setter doesn't check method arity
Getter/setter optimizer cdoesn't check method arity
Jan 19, 2024
I-asked
changed the title
Getter/setter optimizer cdoesn't check method arity
Getter/setter optimizer doesn't check method arity
Jan 19, 2024
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…
The text was updated successfully, but these errors were encountered: