Feature: Add Elixir support (Wasm)

Aperta
  • Qualcosa non va?
#1,060 5 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
50/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
elixir, typescript, wasm
Ambito
web-dev

Direzione di ricerca

Start with LiveCodes' adding-languages checklist, then study how ruby-wasm and python-wasm are wired: the compiler factory, the lang specification file, the result-page runtime script, and the vendors entry. The work is not yet green-lit — the thread is 5 comments deep on day one and asks the maintainer to confirm the Elixir/AtomVM subset target, and the issue author intends to implement it, so confirm claimability before starting. Done means a lang-elixir-wasm specification runs standard-library Elixir offline, plus starter template, docs, and end-to-end tests per the checklist.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

There is currently no option to run Elixir code in LiveCodes. I searched existing issues and found no open request for Elixir support.

Suggested feature

I propose adding Elixir as a script language, targeting the latest stable release (v1.20).

The implementation would follow the existing Wasm runtime pattern used by ruby-wasm and python-wasm:

  • Compiler factory as pass-through: async (code) => code
  • Runtime script loaded in the result page with scriptType: text/elixir-wasm
  • Runtime based on Popcorn / AtomVM, which compiles Elixir to WebAssembly and runs entirely offline in the browser. The public eval demo confirms client-side execution without a server.

Scope for the initial version would cover standard playground usage such as IO, Enum, pipes, and pattern matching. Full OTP features and frameworks such as Phoenix and LiveView would remain out of scope, consistent with AtomVM current subset limitations regarding file I/O, OS processes, and parts of the standard library.

Alternatives considered:

  • Hologram: full-stack framework on top of Phoenix, not suitable for plain Elixir support.
  • Server-side execution: rejected due to the client-side architecture requirement.

If the approach is approved, I will start with a proof of concept including lang-elixir-wasm specification, result page runner script, and vendors entry, then complete the remaining items from the adding-languages checklist including documentation, starter template, and end-to-end tests.

Please confirm whether the Elixir (Wasm) subset limitation is acceptable for the first version, or if a different compiler target is preferred.

Additional context

Lingua principale
TypeScript
Stelle
1.5k
Fork
267
Merge medio
7h 47m
PR unite (30g)
14

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di live-codes/livecodes

Tutte le issue di live-codes/livecodes

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.