workshopsoft/ludic
2
0
Fork 0
Code Issues Pull requests Projects Releases 26 Packages Wiki Activity Actions
ludic/.forgejo/pull_request_template.md
Orkuncakilkaya aca263642d feat(cli): install in one command, and call the CLI ludic 
Getting started meant cloning the repository, bootstrapping a compiler and
learning a task runner called `x`. That is a contributor's workflow handed to
everyone who wants to try the language.

Installing is now one command:

    curl -fsSL https://workshopsoft.pages.workshopsoft.io/ludic/install.sh | sh

install.sh puts a complete toolchain — compiler, CLI, engine runtime, bundled
ludic.* packages, formatter, language server — in ~/.ludic and adds it to PATH.
Prebuilt artifacts are checksum-verified; where a platform has none, or the
release predates this layout, it bootstraps from the compiler's own IR seed with
clang. The docs site publishes the script beside the pages that quote it, so the
page and the script can never come from different releases.

`x` becomes `ludic`, and the surface splits by audience. A user of the language
sees `new`, `run`, `build`, `test`, `add`, `fmt`, `lsp`, `doctor`, `upgrade`;
`ludic new` scaffolds a project that builds and plays as it stands. Everything
the toolchain repo needs moved under `ludic dev` — build, test, reseed,
bootstrap-cfree, docs-gen, release — unchanged apart from the namespace. Those
tasks read arguments one position further along, so dispatch_dev sets a shift
and commands use arg_n()/arg_total() rather than each knowing its own depth.

Release artifacts become complete install roots (bin/ beside runtime/, packages/
and VERSION) rather than bare binaries, which is what the installer unpacks.
`ludic dev test` asserts the whole shape: it stages an install, puts it on PATH
with no LUDIC_HOME, and runs new -> build -> test through it.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-09-05 22:01:52 +03:00

982 B
Raw Blame History

What & why

Closes #

Checklist

  • bin/ludic dev test passes.
  • For compiler/runtime changes: bin/ludic dev reseed && bin/ludic dev bootstrap-cfree still reaches the self-hosting fixpoint with no C compiler in the loop.
  • ludic-fmt leaves the touched files unchanged (2-space, LF, UTF-8).
  • New/changed stdlib symbols are documented under docs/language/** and registered in tools/docgen/inventory.json (bin/ludic dev docs-gen && bin/ludic dev docs-check build/pages passes).
  • Commits follow Conventional Commits.
  • No new C / Python / JS in tooling (Ludic only), and no generated artifacts committed outside build/ / bin/.

Notes for reviewers