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
I found we need to handle `LimitedAccuracy` (i.e. collect its
limitations into the current frame and unwrap its type) whenever
we do inter-procedural inference. Especially, we need to handle
it where we use `abstract_call_method` and `abstract_call_method_with_const_args`.
Otherwise we may encounter nested `LimitedAccuracy`, which is really not
expected. So this commit also adds the assertion that checks we never
form nested `LimitedAccuracy`.
I encountered errors due to this when analyzing JET itself by JET,
probably because its codebase makes heavy use of `invoke`.
I couldn't pack them up as simple test cases though.
(cherry picked from commit 6341fa5)
0 commit comments