Orkuncakilkaya
ea2c6ab246
A `test "name" { ... }` top-level block is discovered automatically and run by a
synthetic runner @main — no `entry` to write, nothing to register. Inside a test,
expect(cond) / expect_eq(a, b) / expect_near(a, b, tol) assert; on failure they
print `file:line: <what> failed (got G, want W)` and set a per-test fail flag but
keep going, so one run reports every failure. The runner prints `ok - name` /
`FAIL - name` per test, a `== N passed, M failed ==` summary, and exits non-zero
if any test failed — so `ludic spec_test.ludic` drops straight into bin/x and CI.
expect_near carries the tolerance fixed-point / accumulated-integer game math need.
Frontend: new `test` keyword (parse_test -> N_TEST, collected in g_tests) and the
call node now carries its source line for the file:line messages. Backend:
emit_test_runner synthesises @fn__test_i bodies + the runner @main; the expect*
builtins lower to a branch-print-flag tail (emit_expect_fail). g_src_name (set in
main from the input path) supplies the filename. The compiler's own source has no
`test` blocks, so its self-compiled IR is unchanged and the C-free fixpoint holds.
- `test` wired into the vocabulary (ludic_syntax.h, JetBrains lexer, TextMate
grammar) and documented (docs/language/testing/)
- examples/library/testing.ludic: a passing spec, guarded by a new spec_case in
the regression suite (build, run, require exit 0 + the expected summary)
Coverage instrumentation (the biggest lift in #12) is left as a follow-up.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
||
|---|---|---|
| .. | ||
| icons | ||
| snippets | ||
| src | ||
| syntaxes | ||
| .vscodeignore | ||
| language-configuration.json | ||
| package-lock.json | ||
| package.json | ||
| README.md | ||
Ludic for VS Code
Syntax highlighting, formatting, and full language-server support for Ludic,
the AI-first, ECS-native game language. See LANGUAGE.md in the Ludic repository
for the language reference.
What you get
| Source | |
|---|---|
| Syntax highlighting | TextMate grammar, works with no build |
| Semantic highlighting | ludic-lsp — real name resolution, so a component reads differently from a local |
| Diagnostics | structural errors as you type; ludicc's own errors on save |
| Completion | context-aware: fields after ., components inside query [...], phases after phase, widgets inside ui |
| Hover | signatures and docs for builtins, intrinsics, and everything you declared |
| Go to definition / references / rename | across every file in the compilation unit, following import |
| Formatting | format-on-save, comment-preserving |
| Outline, folding, inlay hints, signature help | |
```ludic fences in Markdown |
highlighted, checked, and formatted |
Setup
Build the toolchain once, from the repository root:
bin/x tools
That produces bin/ludic-lsp and bin/ludic-fmt, which the extension finds
on its own. If you keep them elsewhere, set ludic.server.path.
Format on save:
"[ludic]": { "editor.formatOnSave": true }
Settings
ludic.server.path— whereludic-lsplives. Empty = searchbin/, thenPATH.ludic.server.enabled— turn the server off and keep only static highlighting.ludic.compilerPath— whereludicclives, for on-save diagnostics.ludic.compilerDiagnostics— whether to run the compiler at all.ludic.indentSize— spaces per level for the formatter.ludic.trace.server— log LSP traffic (Ludic: Show Language Server Log).
Installing without publishing
cd tools/editors/vscode
npm install
npx @vscode/vsce package
code --install-extension ludic-1.0.0.vsix