leanprover / leanprover/lean4

Autocomplete shows incorrect type

Open
#7,632 1 comment 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

Consider this code:

variable (a : Vector Bool 3)

#check a.set

When I put my cursor at the end of the code and trigger autocomplete via Ctrl+Space, then I get various suggestions. At the top are the two suggestions I expect: set and set! (both Vector.set and Vector.set! exist). However, the type signature shown as part of the autocomplete box is not always correct, and it seems to depend on the version. When I try this on live.lean-lang.org with the "latest nightly" setting, which is Lean version 4.19.0-nightly-2025-03-22, I see the following two types:

Image

Image

The first is clearly wrong, the second one is right.

In my local project, which uses the toolchain leanprover/lean4:v4.17.0, I get the following:

Image

Image

So here the first is right and the second is wrong.

Versions

See above.

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 Vector Bool 3 example in the issue on the referenced Lean versions and compare the two autocomplete signatures. Trace the autocomplete path that produces the set and set! suggestions. Done means both displayed types consistently match the corresponding Vector.set and Vector.set! declarations.

Written by the indexing model from the issue text.

Assessment

Domain
compilers, developer-experience
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.