leanprover / leanprover/lean4

Autocompletion for name literals includes suggestion for `Name`, not the namespace of the name being constructed

Open
#7,456 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug P-low
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

If I type

import Lean

#check ``Complement. 

then I get autocompletion suggestions like anyS, which is a function on Lean.Name. Accepting this suggestion completes to

#check ``Complement.anyS

which is an error.

If I type

import Lean

#check ``Complement.comp

then I get exactly two suggestions: components and componentsRev (both are functions on Lean.Name).

However, if I type

import Lean

#check ``Complement.compl

then I get the expected suggestion, namely complement.

Expected behavior: In all three cases, complement should be suggested and nothing else.

Actual behavior: See above

Versions

4.19.0-nightly-2025-03-12 on 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

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

Reproduce the three minimal examples in live.lean-lang.org using Lean nightly and compare the autocompletion results for Complement., Complement.comp, and Complement.compl. Investigate the name-literal completion entry point responsible for these suggestions; done means all three forms suggest only complement and accept it without producing an error.

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.