Repository navigation
gen_degree: write Degree files under Sendov/FiniteRange - #7
Open
Chessing234 wants to merge 1 commit into
Open
Chessing234 wants to merge 1 commit into
Chessing234 wants to merge 1 commit into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Running
gen_degree.pyoutside the repository root writesDegree{n}.leaninto the caller's working directory. Resolve the output directory from the script path and createSendov/FiniteRangewhen needed, so the generated proof lands in the source tree.Validation: the numerical
--checksuite passes. Generation from a different working directory passes with both an absent and an existing output directory; the file is written underSendov/FiniteRangeand no file appears in the caller's directory.git diff --checkpasses. No Lean source changes are included.Replaces #5 with a clean commit history. The separate import-guard proposal in #2 addresses a different behavior.