Orkuncakilkaya
ae0bae0457
32-bit word access is indexing now, not peek32/poke32: peek32(ui_rx, i) -> ui_rx[i] (reads an int) poke32(rt_fb, i, c) -> rt_fb[i] = c (writes an int) A buffer typed `words` (a pointer whose elements are i32) indexes with `w[i]` as a full int; a plain `ptr`/`str` keeps byte indexing. emit_index_addr picks the element type from the base's type — byte-identical IR to the old intrinsics, so the migration reproduces the compiler and every golden render exactly. The ~60 word buffers (rt_fb, tt_*/gc_* font tables, png_px/spr_px pixels, ui_* layout arrays) were retyped from `ptr` to `words` scope-aware (per-function, so the s/out/p byte-vs-word name collisions across functions stay correct), then the 254 peek32/poke32 sites migrated to indexing. A scope-analysis miss left 12 buffers (gc_*, sc_d, ui_rx/ui_ry) un-retyped — caught as a menu golden diff and fixed. No true mixed byte+word access exists on any one variable, so a per-buffer element type is sound. Reseeded (22527 lines); C-free fixpoint holds; goldens byte-identical; 18/18; vocab (byte/words types in, peek32/poke32 out) + doc-fences clean. 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:
./tools/build-tools.sh
That produces build/ludic-lsp and build/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 = searchbuild/, 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