feat(lean_examples): use grind for some of the proofs#1802
Merged
Conversation
maximebuyse
approved these changes
Dec 16, 2025
Contributor
maximebuyse
left a comment
There was a problem hiding this comment.
I don't completely get the implications of this, but we can try this and reverting shouldn't be hard if we change our minds.
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.
I have experimented with grind on the lean_chacha example. I haven't replaced all of the proofs, only some of them. For the grind annotations that really belong into the Lean repo, I have created a
MissingLeanfolder that I hope to (partially) upstream into the Lean repo some time.What I hope to get from grind:
[simp]annotations that don't really simplify, but rather make more complicated such as https://github.com/cryspen/hax/blob/main/hax-lib/proof-libs/lean/Hax/Lib.lean#L288-L310It's not clear to me if grind really gives us that, but I am hopeful.
Cons:
simping orsubst_eqsbefore invoking grind?)@[grind]