gleam-lang/gleam

LSP: sort complete suggestions after a pipe based on types

Open

#3,297 opened on Jun 19, 2024

View on GitHub
 (8 comments) (5 reactions) (0 assignees)Rust (21,417 stars) (960 forks)batch import
help wanted

Description

I don't know how functional languages LSPs usually handle this case but it would be nice if suggestions after a pipe are functions that contain the type as the first parameter. i.e:

"hello" |> // <- This would only suggest functions that have String as the first parameter type

If there are multiple pipes, the suggestions should be related to the last output value.

"2" |> int.parse |>  // <- This would only suggest functions that have Result as the first parameter type

Contributor guide

Tech stack
rust
Domain
developer experiencetooling
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
over 1 week
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
RustLSP protocolGleam type inference
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
25
Research direction
Investigate the current LSP completion handler in the Gleam compiler, likely in the `compiler core/src/language server` directory. Understand how type information is obtained for the expression after a pipe. Look at how completion items are currently filtered and sorted. Then design a heuristic to sort functions based on whether their first parameter type matches the inferred type of the expression before the pipe.
LSP: sort complete suggestions after a pipe based on types · gleam-lang/gleam#3297 | Good First Issue