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
When TFA de-virtualizes instance calls into static calls we might loose the inferred type information on the receiver.
Currently we have ad-hoc code for strengthening the type of the receiver based on the target of a static call instruction, e.g. in the AOT call specializer . We should ensure the type information is already attached from the very beginning, instead of "re-computing" based on the target of a static call. Also the TFA might have a more precise receiver type than the we can re-compute based on the target (since that can be in a super class).
When TFA de-virtualizes instance calls into static calls we might loose the inferred type information on the receiver.
Currently we have ad-hoc code for strengthening the type of the receiver based on the target of a static call instruction, e.g. in the AOT call specializer . We should ensure the type information is already attached from the very beginning, instead of "re-computing" based on the target of a static call. Also the TFA might have a more precise receiver type than the we can re-compute based on the target (since that can be in a super class).
@mraleph @alexmarkov
The text was updated successfully, but these errors were encountered: