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
So far, translation for alias-like PTypes worked by first adding/
translating the target type and then creating a type symbol for the
alias type mirroring the description of the target type.
In the recursive translation scenario `A -> B -> ... -> C -> B`, where
`A` and `C` are alias-like types and `B` is an object type, the second
request to translate `B` yielded the still-incomplete but already
registered type symbol for the object type, causing `C` to stay in an
incomplete state, breaking type environment expectations.
To fix the issue, translation of object types is always delayed till
the end of the entry `add` call; a follow-up pass then patches the type
symbols corresponding to alias-like PTypes aliasing object types.
0 commit comments