pyk.proof.parallel module¶
- class Proof[source]¶
Bases:
ABC
Should represent a computer proof of a single claim
- abstract property status: ProofStatus¶
ProofStatus.PASSED: the claim has been proven ProofStatus.FAILED: the claim has not been proven, but the proof cannot advance further. ProofStatus.PENDING: the claim has not yet been proven, but the proof can advance further. Must not change, except with calls to prover.commit(self, update) for some prover,update. If proof.status() is ProofStatus.PENDING, prover.steps(proof) must be nonempty. If proof.status() is ProofStatus.PASSED, prover.steps(proof) must be empty. Once proof.status() is ProofStatus.PASSED or ProofStatus.FAILED, it must remain so.
- class ProofStep[source]¶
Bases:
ABC
,Generic
[U
]Should be a description of a computation needed to make progress on a Proof. Must be hashable. Must be frozen dataclass. Must be pickable. Should be small.
- class Prover[source]¶
Bases:
ABC
,Generic
[P
,U
]Should contain all data needed to make progress on a P (proof). May be specific to a single P (proof) or may be able to handle multiple.
Type parameter requirements: U should be a description of how to make a small update to a Proof based on the results of a computation specified by a ProofStep. U must be picklable. U must be frozen dataclass. U should be small.
- abstract commit(proof: P, update: U) None [source]¶
Should update proof according to update. If steps() or commit() has been called on a proof proof, commit() may never again be called on proof. Must only be called with an update that was returned by step.execute() where step was returned by self.steps(proof). Steps for a proof proof can have their results submitted any time after they are made available by self.steps(proof), including in any order and multiple times, and the Prover must be able to handle this.
- abstract steps(proof: P) Iterable[ProofStep[U]] [source]¶
Return a list of ProofStep[U] which represents all the computation jobs as defined by ProofStep, which have not yet been computed and committed, and are available given the current state of proof. Note that this is a requirement which is not enforced by the type system. If steps() or commit() has been called on a proof proof, steps() may never again be called on proof. Must not modify self or proof. The output of this function must only change with calls to self.commit().