`lambdaMetaTelescope` doesn't preserve binder names
Nobody has claimed this yet.
- Dominant language
- Lean
- Stars
- 9.2k
- Forks
- 990
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 175
Description
Prerequisites
- 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
lambdaMetaTelescope creates metavariables with anonymous user names instead of using the binder names from the lambda binders.
Context
This caused to_dual in mathlib to generate some definitions where the lambda binder names were wrong. That problem has now been fixed (https://github.com/leanprover-community/mathlib4/pull/40946)
Steps to Reproduce
import Lean
open Lean Meta
/-- info: fun {x} => x -/
#guard_msgs in
run_meta
let e := Expr.lam `a (.sort 0) (.bvar 0) .default
let (mvars, _, e) ← lambdaMetaTelescope e
let e ← mkLambdaFVars mvars e
logInfo m!"{e}"
Expected behavior: The resulting bound variable is called a
Actual behavior: The resulting bound variable is called x
Versions
4.32.0-rc1
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 locating the implementation of lambdaMetaTelescope and run the minimal run_meta reproduction from the issue. Verify that rebuilding the lambda preserves the binder name a rather than producing x, while keeping the example self-contained and dependency-free.
Written by the indexing model from the issue text.
Assessment
- Domain
- compilers
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 78/100