leanprover / leanprover/lean4

`protected` annotation is ignored when module system is active

Open
#9,836 0 comments 1 reaction 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
module

structure A where

namespace A

protected def true : A := ⟨⟩

/--
error: Type mismatch
  true
has type
  A
but is expected to have type
  Bool
-/
#guard_msgs in
def foo : Bool := true

end A

The error goes away when removing the module.

Expected behavior: true resolves to Bool.true.

Actual behavior: true resolved to A.true.

Versions

nightly-2025-08-10

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 self-contained reproducer against the latest Lean nightly and compare behavior with and without the module declaration. Trace the name-resolution path for protected def true and verify that true resolves to Bool.true in foo; the issue is done when the #guard_msgs expectation passes with the module system active.

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
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.