Resumption not taking type unification into account #88
Labels
No Label
category
bug
category
doc
category
feature
category
optimization
category
organization
part/Delation
part/Elab
part/Environment
part/FFI
part/Frontend
part/Goal
part/REPL
part/Serial
priority
high
priority
irrelevant
priority
low
priority
medium
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: aniva/Pantograph#88
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
In aniva/Trillium#124, during atomization of
We got the trace
Note that after
exact a
, the resumed state still has?0 α
as a goal. This should definitely not happen. Is there any reason whyα
was not solved in passing?Resumption not taking into account type unificationto Resumption not taking type unification into accountThis was a bug in the downstream
Tactic.exact
implementation.