Open
Description
- Re-executing a KClaim (with
--save-directory
) where a proof changes or a dependency changes, does not trigger--reinit
behavior. We should be parsing the claims, and invalidating any claims where the claim itself or a dependency has changed. - Parallel proof discharge waits for each batch of proofs instead of adding to the queue of tasks asynchronously. This means that if there a few really long running proofs in one layer of proofs, we won't move on to the proofs in the next layer who's dependencies are already discharged.
- Proofs whos dependencies are not discharged should not be run unless the dependency is admitted or the user specifies to admit dependencies. Perhaps?