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
Changing alias relate or the way we define opaque types can cause this to result in ambiguity instead. Fundamentally we want exists<'0, '1> alias-relate(Tait<'0>, Tait<'1>) to hold inside of the defining scope of Tait, regardless of whether we actually define Tait.
The text was updated successfully, but these errors were encountered:
This example fails with overflow in the new solver right now
Changing alias relate or the way we define opaque types can cause this to result in ambiguity instead. Fundamentally we want
exists<'0, '1> alias-relate(Tait<'0>, Tait<'1>)
to hold inside of the defining scope ofTait
, regardless of whether we actually defineTait
.The text was updated successfully, but these errors were encountered: