Allow deletion of certain proof states and remove proof tree structure #8
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#8
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?
Since we are not going to do any book keeping about whether a proof tree is actually proven (in order to keep
Pantograph
's bookkeeping mechanism as light as possible), we should remove theProofTree
and directly storeProofState
s in theState
monad in the main loop. Then we should use some other data structure to save suchProofState
s so the client can ask for the deletion of a proof state.This would be a breaking change, so the version should be bumped to
0.2.4
.We can even directly save bare goals (actually just a mvarId with a saved state) since we do not store the tactic along with each
ProofState
:instead of
of course keeping track of a parent will require the index be unique, so this should be dropped as well.
Leaving this until Trillium backend can handle this bookkeeping.
Done!