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
While debugging a separate issue, I noticed that in our tests all WF checks are done by the SLG solver. Out of curiosity I tried using the recursive solver for the WF checks and noticed a handful of failures (i.e. the solver incorrectly determines the program to be not WF) and cases which run forever.
Failures:
test::cycle::overflow
test::misc::subgoal_abstraction
test::misc::subgoal_cycle_inhabited
test::misc::subgoal_cycle_uninhabited
Infinite execution:
test::misc::lifetime_outlives_constraints
test::misc::type_outlives_constraints
The text was updated successfully, but these errors were encountered:
While debugging a separate issue, I noticed that in our tests all WF checks are done by the SLG solver. Out of curiosity I tried using the recursive solver for the WF checks and noticed a handful of failures (i.e. the solver incorrectly determines the program to be not WF) and cases which run forever.
Failures:
Infinite execution:
The text was updated successfully, but these errors were encountered: