leanprover-community / leanprover-community/iris-lean
Unfolding head term when idestruct fails
Nobody has claimed this yet.
- Dominant language
- Lean
- Stars
- 218
- Forks
- 63
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 22
Description
This is a very minor grievance, but I'd like it if the proofmode tried unfolding more terms when a destruct fails. For example here:
simp only [absorbingly]
iintro ⟨_, HW⟩ _
iintro fails if absorbingly isn't unfolded first. It it possible for the proofmode to try unfolding when it fails, to be a little more like how refine or apply works in Lean?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Read src/Iris/BI/Lib/Fixpoint.lean around line 105 and reproduce the failing iintro example involving absorbingly. Trace the iintro entry point to determine where destruct failure is handled. Done means the proofmode retries with the relevant unfolding so this example succeeds, with regression coverage for the behavior.
Written by the indexing model from the issue text.
Assessment
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100