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 could add an additional check on the length inside splitOp, so that it won't call Data.Vector.slice with invalid indices. But that wouldn't fix the problem; it would still panic, just maybe with a slightly nicer error message.
The real problem here lies much earlier, when the ill-typed saw-core term is constructed in the first place. @langston-barrett, do you still know to trigger this bug? I could probably diagnose it if I was able to reproduce it. Otherwise we might as well close the ticket.
When SAW is checking proof obligations on my proof and the
w4_unint_z3
tactic, it fails with:With the
unint_z3
tactic, I seeThis is with
saw-core
affad38.The text was updated successfully, but these errors were encountered: