Abstract out the proof verification process #63
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
One can imagine several clients/needs for an iteration through the proof tree, which follows the steps of the proof and accumulates on the stack:
All these targets could be reached based on a single mechanism provided by the metamath-knife library. E.g. the client would provide an implementor of a given trait.
I've tried to implement this kind of abstraction in this PR, starting from
proof.rs
:u8
buffer. This PR introduces a generic typeStackBuffer
, implementing a newProofStack
trait for this.Idx
for thatProofStack
, to address one element on the stack.add_floating
,add_essential
,do_substitute
,finish
), etc. have been moved to default methods of theStackBuffer
trait