`liftCommandElabM` breaks namespace resolution?
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
When I use liftCommandElabM with elab and resolveGlobalConstNoOverload, it seems to break namespace resolution. It looks like a bug to me. Is the following expected?
import Lean
def Foo.ExampleDL := 42
elab "s3(" dl:ident ")" : term => do
-- remove the `Lean.liftCommandElabM` to remove error below
let _ ← Lean.liftCommandElabM (Lean.resolveGlobalConstNoOverload dl)
return .const ``Nat []
#check s3(Foo.ExampleDL)
namespace Foo
-- "Unknown constant `ExampleDL`". Reproducible in https://live.lean-lang.org/
#check s3(ExampleDL)
Context
Versions
4.24.0-rc1, live.lean-lang.org
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 self-contained reproducer against the reported Lean nightly or live. Compare the two #check cases and inspect the interaction between liftCommandElabM, elab, and resolveGlobalConstNoOverload. Done means the unqualified ExampleDL resolves inside namespace Foo without removing liftCommandElabM.
Written by the indexing model from the issue text.
Assessment
- Domain
- compilers
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100