gleam-lang/gleam

Include the destination in error message when copying/linking fails

Open

#5379 opened on Feb 20, 2026

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

Description

The problem

While working on #5378, I've noticed few TODOs about the need to add destination to error message, when copying or symlinking fails. It seems very useful for me.

Possible solution

  1. Add new optional field to error
  2. Update code for coversion to diagnostic
  3. Update all usages to include it

If it's desired feature, I will work on this!

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.
half day
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.
clear
Prerequisites
Basic knowledge of RustUnderstanding of Gleam compiler error handling
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65
Research direction
Examine the linked issue #5378 for the original context and any TODOs in the codebase regarding error messages for copying/linking. Locate the error type definitions (likely in a module like `error.rs`) and the conversion to diagnostic function. Review existing usages of these errors to understand the current pattern. The changes involve adding an optional destination field, updating the diagnostic conversion, and ensuring all relevant call sites include the destination. Pay attention to maintainer feedback in the issue comments for any additional guidance.