gleam-lang/gleam

Requirement overriding

Open

#2,899 opened on Apr 5, 2024

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

Description

I think it would be a useful addition to the language to have a mechanism by which requirements which conflict can be ignored.

I'm not sure the best way to go about this. Node has the concept of overrides (https://docs.npmjs.com/cli/v8/configuring-npm/package-json#overrides) which strikes me as a possible solution.

I think in my case I just wanted the build to override a single include - gleescript required filepath >=0.1-<1.0 but filepath 1.0 was needed for simplifile >=1.6.

Contributor guide

Tech stack
rust
Domain
build system
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
5
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.
mostly clear
Prerequisites
Gleam language knowledgeRust programmingCompiler internalsDependency resolution concepts
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
10
Research direction
Review the discussion in issue #2899 for alternative approaches. The implementation would likely involve modifying the dependency resolver in the Gleam compiler (located in src/gleam/dependency/). Consider existing patterns like npm overrides for inspiration. No maintainer has provided specific guidance on acceptance criteria.