History

Orkuncakilkaya c7c8e2779c All checks were successful bootstrap / cfree-fixpoint (push) Successful in 17s Details ci / build-and-test (push) Successful in 1m13s Details commit-lint / conventional-commits (push) Successful in 3s Details docs / build-and-deploy (push) Successful in 19s Details feat(errors): panic(msg) + assert(cond, msg) with file:line — no raw crashes (#8 ) RFC decision (the split the issue recommended): programmer bugs abort loud and located; recoverable failures become values. This ships the first half. panic(msg) prints `file:line: panic: <msg>` to stderr and aborts the process with exit code 1 — a clear, located error instead of a segfault or a silent wrong result. assert(cond, msg) is the guarded form: it aborts with `file:line: assertion failed: <msg>` only when cond is false, otherwise execution continues. The location is baked in at compile time (the call node carries its source line, g_src_name carries the file); the message is any string. Both lower in emit_call to an fprintf-to-stderr + exit(1) + unreachable tail (assert branches on the condition first). @fprintf and the format constant are declared on demand (g_uses_panic), so a program that never panics is unchanged — and the compiler's own source uses neither, so the C-free bootstrap fixpoint holds. - panic/assert registered as builtins across the vocabulary (ludic_syntax.h, the JetBrains lexer, the TextMate grammar) and documented (docs/language/builtins/) - examples/library/errors.ludic covers the success path (asserts hold, program runs to the end); a panic_case in the suite covers the failure path (non-zero exit + the located stderr message). x test is now 69 checks. Deferred: recoverable failures as `try`/`else` values (needs the tagged-union type system, #1) and a top-level `recover` for the dev game loop. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>		2026-08-31 14:33:37 +03:00
..
error-handling.md	feat(errors): panic(msg) + assert(cond, msg) with file:line — no raw crashes (#8 )	2026-08-31 14:33:37 +03:00
light-namespace.md	feat(rendering): add Light.* — deterministic 2D light accumulation with hard shadows (#4 )	2026-08-31 14:07:19 +03:00
README.md	feat(release): SemVer + ludicc --version, changesets, and x release	2026-08-30 23:46:59 +03:00
testing-framework.md	feat(testing): built-in test blocks + expect assertions, auto-run with pass/fail (#12 )	2026-08-31 14:27:45 +03:00

README.md

Changesets

A changeset is one small Markdown file describing a single user-facing change, dropped in this directory. x release consumes every changeset here into a new CHANGELOG.md section, bumps VERSION, and deletes the consumed files.

Format

bump: minor
type: feat
One or more lines describing the change, in the past-agnostic imperative used in
the changelog. Markdown is fine.

bump: — major, minor, or patch (SemVer). The release version is bumped by the highest level among the pending changesets (unless x release <level> overrides it).
type: — the Conventional Commit type (feat, fix, perf, docs, …); it becomes the bold prefix of the changelog bullet.

Adding one

Create a file with a short, unique name, e.g. changes/regex-namespace.md. Any filename works except this README.md, which the release step always skips.