leanprover / leanprover/lean4

`open` does not open all overloaded namespaces

Open
#11,014 3 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug P-medium
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:

Description

Consider the following code:

import Lean

def A.B.foo1 := 3
def B.foo2 := 3

section Test1
namespace A
-- ... [Lean.Syntax.Preresolved.namespace `A.B]
#eval `(ident|B)
end A
end Test1

section Test2
open A
-- ... [Lean.Syntax.Preresolved.namespace `B, Lean.Syntax.Preresolved.namespace `A.B]
#eval `(ident|B)
end Test2

Note that the first identifier B produces a syntax that contains only one preresolved namespace A.B, which is wrong, while the second identifier B produces two preresolved namespaces B and A.B, which is the correct result.

This leads to the fact that open B in the first section not allowing foo2, which is wrong:

import Lean

def A.B.foo1 := 3
def B.foo2 := 3

section Test1
namespace A
open B
#check foo2 -- Unknown identifier
end A
end Test1

section Test2
open A
open B
#check foo2
end Test2
Context

Zulip: lean4 > open not opening a namespace

Versions

Lean 4.26.0-nightly-2025-10-29
Target: x86_64-unknown-linux-gnu

Impact

Add 👍 to issues you consider important. If others are impacted by this issue, please ask them to add 👍 to it.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by running the minimal reproducer against Lean nightly and compare the preresolved namespaces shown for #eval (ident|B)inside and outsidenamespace A. Use the two #check foo2cases as the regression criteria:open BinsideAshould resolvefoo2` from the overloaded namespaces.

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
Clearly specified
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.