gleam-lang/gleam

Consolidate protocols for elixir dependencies

Open

#1,743 opened on Aug 29, 2022

View on GitHub
 (0 comments) (1 reaction) (0 assignees)Rust (960 forks)batch import
help wanted

Repository metrics

Stars
 (21,417 stars)
PR merge metrics
 (Avg merge 10d 19h) (69 merged PRs in 30d)

Description

Do we ever consolidate protocols? Could have an issue for adding it later to avoid it blocking this addition.

Originally posted by @lpil in https://github.com/gleam-lang/gleam/pull/1741#discussion_r957089836

At the moment we don't. Here's how rebar_mix used to do it. https://github.com/Supersonido/rebar_mix/blob/00ea7c800446f87a31db00b9c5987d0b76736226/src/rebar_mix_protocol_consolidation.exs

We could use the same or a similar Elixir script and make a directory alongside everything in build/dev/erlang. With something like consolidated/ebin there, it might just work?

Contributor guide

Research direction
Implement protocol consolidation for Elixir dependencies by adapting the rebar mix script and adding it to the build process.
Tech stack
elixir
Domain
backend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
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
Elixir
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60