Skip to content

Conversation

@tom93
Copy link

@tom93 tom93 commented Nov 11, 2025

Hi, this is my attempt at a fix for #15. Please check that my my idea is correct; from the commit message:

If some runs succeeded and some runs didn't produce a well-formed example, then the overall result should be that some runs succeeded, not that we couldn't generate a well-formed example.

(The handling of TestResult.success (.inr h) is unchanged -- it already had higher priority than .gaveUp, and further it triggers immediate termination because it has a positive proof.)

Fixes #15.

@tom93 tom93 force-pushed the pr/fix-success-gaveUp-priority branch from ab6f67e to bde0bca Compare November 11, 2025 12:31
@tom93 tom93 changed the title Give TestResult.success (.inl ()) higher priority than .gaveUp fix: give TestResult.success (.inl ()) higher priority than .gaveUp Nov 11, 2025
If some runs succeeded and some runs didn't produce a well-formed
example, then the overall result should be that some runs succeeded,
not that we couldn't generate a well-formed example.

(The handling of `TestResult.success (.inr h)` is unchanged -- it
already had higher priority than `.gaveUp`, and further it triggers
immediate termination because it has a positive proof.)

Fixes leanprover-community#15.
@tom93 tom93 force-pushed the pr/fix-success-gaveUp-priority branch from bde0bca to c6dc2f5 Compare November 11, 2025 12:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Range guard on natural

1 participant