LSP module auto-import: handle module name collisions

Description

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.

3

Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.

1-3 hours

Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.

fresh

ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.

mostly clear

Prerequisites

Familiarity with LSP protocolUnderstanding of Gleam's import system

Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.

30

Research direction

The issue is a follow up to PR #3219 which added auto import completions. The problem is that the LS can suggest an import name that conflicts with an existing binding. The issue asks whether to prompt the user for an alternative name or generate one automatically. To resolve this, examine the LSP completion handler in the Gleam compiler, likely in files like `compiler core/src/language server/completions.rs`. Review the logic that generates import names and consider adding a collision check against the current scope's bindings. The solution may involve either a user prompt (more complex) or automatic disambiguation (e.g., appending a number). Discuss in the issue or linked PR comments before implementation.