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
Typing a TypeBoundsTree(Empty, Empty) leads to a TypeBoundsTree(Nothing,
Any), if this tree appears in a higher-kinded position, we manually set
its type, but we don't change the upper bound which is still "Any" and
ends up being pickled. To avoid this issue this commit simply replaces
the TypeBoundsTree with a synthetic TypeTree with the proper type and
position, which is all that we need.
0 commit comments