`conv`-mode `congr` leaves unsynthesized placeholder
Nobody has claimed this yet.
- Dominant language
- Lean
- Stars
- 9.2k
- Forks
- 990
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 175
Description
Prerequisites
Please put an X between the brackets as you perform the following steps:
- Check that your issue is not already filed:
https://github.com/leanprover/lean4/issues - Reduce the issue to a minimal, self-contained, reproducible test case.
Avoid dependencies to Mathlib or Batteries. - Test your test case against the latest nightly release, for example on
https://live.lean-lang.org/#project=lean-nightly
(You can also use the settings there to switch to “Lean nightly”)
Description
The congr tactic within conv mode leaves a stray uninstantiated metavariable, leading to a cryptic error
Context
Steps to Reproduce
Run
theorem T: (fun i => if h : i < 1 then 42 else 0) = fun i => 42 := by
conv =>
lhs
intro i
congr
sorry
Expected behavior: the sorry should succeed
Actual behavior:
don't know how to synthesize placeholder for argument 'α'
context:
⊢ Prop
on the sorry
Versions
4.14.0-rc2
4.15.0-nightly-2024-11-22
Additional Information
If using the recover sorry tactic from import Mathlib.Tactic.Recover, it turns out that there is a stray (i : Nat) → Decidable (i < 1) goal.
Impact
Add 👍 to issues you consider important. If others are impacted by this issue, please ask them to add 👍 to it.
Contributor guide
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
Start by running the minimal reproducer from the issue against the reported Lean versions and inspect the conv-mode congr behavior. Use the reported stray (i : Nat) → Decidable (i < 1) goal as the failure criterion; done means the sorry succeeds without leaving an unsynthesized placeholder.
Written by the indexing model from the issue text.
Assessment
- Domain
- compilers
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100