leanprover / leanprover/lean4

`private class` fails to initialize the type's namespace

Open
#10,061 0 comments 0 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

After defining a private class or structure either via an explicit private or through the module system, a user cannot open or export from the type's namespace, because it has yet to be initialized.

Context

This issue was discovered during the port of Lake to the module system (#9749).

Steps to Reproduce
prelude
import Init.Notation

private class Foo where
  foo : Nat

/-- error: unknown namespace 'Foo' -/
#guard_msgs in export Foo (foo)

/-- error: unknown namespace 'Foo' -/
#guard_msgs in open Foo (foo)

namespace Foo end Foo

open Foo (foo) -- works
export Foo (foo) -- works

This example occurs with both class and structure and, in a module, without an explicit private.

Expected behavior:

open and export work without needing to first define the namespace.

Actual behavior:

Namespace must first be explicitly defined before open or export work.

Versions

leanprover/lean4:nightly-2025-08-22

and recent master (f12177d01e)

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 reproduction from the issue against the referenced Lean nightly or current master, focusing on private class/structure declarations followed by open and export. The fix is complete when those commands work without an explicit namespace Foo declaration, including the module-system case, while the existing reproduction remains valid.

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.