Orkuncakilkaya
920d476a15
Cohesion audit found two keywords that are pure duplicates:
- `when c { }` produced a byte-identical S_IF to an else-less `if c { }`
(no distinguishing flag) — so it was a second spelling of the same node.
- `enter Name` produced identical codegen to `become Name`: it set an
`ival` flag that emit_become never reads.
Both removed from the parser. `if` already parses with an optional `else`, so
nothing is lost. examples/scenes.ludic (an uncompiled design sketch) and the
LANGUAGE.md scenes section now use `become Name` for scene transitions.
Vocabulary synced (ludic_syntax.h, TextMate grammar, LudicTokens.kt);
check-vocabulary clean. Reseeded (22148 lines); C-free fixpoint holds;
goldens identical; 17/17.
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