gleam-lang/gleam

LSP: Renaming aliased value when alias has same name breaks alias

Open

#5,681 建立於 2026年5月3日

在 GitHub 查看
 (2 留言) (0 反應) (0 負責人)Rust (21,417 star) (960 fork)batch import
help wanted

描述

Sorry, I know the title is hard to understand. An example will make much more sense:

// foo.gleam
pub type Foo { Bar }
//             ^^^ (a)

// main.gleam
import foo.{Bar as Bar}
//      (b) ^^^    ^^^ (c)
pub fn main() {
    let _ = Bar
    //      ^^^ (d)
}

To reproduce: Move the cursor over (a) and trigger a rename to a new name.

Expected outcome: (a) and (b) change to the new value, (c) and (d) remain unchanged.

Actual outcome: (a), (b), and (d) change to the new value. (c) remains Bar. However, since (d) changes to the new value as well, the rename causes an unknown variable error at (d).

Gleam version: 1.16.0 OS: macOS Tahoe 26.4 (25E246) Editor: helix 25.07.1 (a05c151b)

貢獻者指南

技術棧
rust
領域
developer experiencetooling
議題類型
bug
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-3 hours
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
fresh
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
Gleam language syntaxunderstanding of LSP rename
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
60
研究方向
Investigate the LSP rename implementation in the Gleam compiler, likely in files related to code actions or rename handling. Look for how aliased imports are handled during rename operations. The issue describes a case where renaming a type definition also renames the import alias when the alias has the same name as the original. Focus on the logic that determines which identifiers to update when renaming a symbol.
LSP: Renaming aliased value when alias has same name breaks alias · gleam-lang/gleam#5681 | Good First Issue