gleam-lang/gleam

LSP fails to suggest completion for locally defined `use`d argument

Open

#5,258 建立於 2026年1月3日

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

描述

LSP fails to suggest completion for locally defined used argument. For example, if I use Lustre and want to create a custom effect I may write something like this:

fn load_data(msg: fn(String) -> msg) -> Effect(msg) {
  use dispatch <- effect.from
  let data = "Example data"
  dispatch(msg(data))
}

If I partially type disp in the last line expecting a suggestion — I wouldn't get it:

Note: suggestion works fine if I convert use to the callback-style call.

Versions:

  • Gleam: 1.14.0
  • VSCodium: 1.107.18627
  • Lustre: 5.4.0
  • macOS: 15.7.3

貢獻者指南

技術棧
rust
領域
developer experiencetooling
議題類型
bug
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
half day
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
fresh
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
Familiarity with Gleam languageKnowledge of LSP completion logicRust programming
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
40
研究方向
Investigate the LSP completion handler for `use` expressions in the Gleam compiler. Look at the file `compiler core/src/language server/completions.rs` (or similar) to understand how variables introduced by `use` are tracked. The issue indicates that when using the `use dispatch < effect.from` pattern, the `dispatch` variable is not suggested. Compare with the equivalent callback style call to identify where the symbol registration differs. Check for any recent changes that might have affected this behavior.
LSP fails to suggest completion for locally defined `use`d argument · gleam-lang/gleam#5258 | Good First Issue