History

Orkuncakilkaya b7745a4600 refactor(lang): rename the `str` type (and stringify builtin) to `string` Expand the abbreviated string type and its conversion builtin to the full word everywhere: str -> string (the immutable-string type) str(x) -> str -> string(x) -> string (the stringify builtin; what `{…}` interpolation calls) Types are recognized by identifier, and llty maps both spellings to LLVM `ptr`, so this is an atomic source rewrite: type annotations, the Ludic type tags, the builtin name/dispatch, and the interpolation desugar, plus the grammars, LSP, docs (type-str -> type-string, fn-str -> fn-string), and inventory. int/bool stay (universally accepted, like Math). Reseeded; C-free fixpoint holds; all suites green (45/24/29); site + check.py OK. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>		2026-08-30 01:51:11 +03:00
..
icons	Baseline: Ludic compiler + toolchain, Phase 1 syntax fixes complete	2026-08-27 15:15:35 +03:00
snippets	Baseline: Ludic compiler + toolchain, Phase 1 syntax fixes complete	2026-08-27 15:15:35 +03:00
src	feat(stdlib): namespaced standard library (issue #2 )	2026-08-30 00:26:19 +03:00
syntaxes	refactor(lang): rename the `str` type (and stringify builtin) to `string`	2026-08-30 01:51:11 +03:00
.vscodeignore	Baseline: Ludic compiler + toolchain, Phase 1 syntax fixes complete	2026-08-27 15:15:35 +03:00
language-configuration.json	Baseline: Ludic compiler + toolchain, Phase 1 syntax fixes complete	2026-08-27 15:15:35 +03:00
package-lock.json	Baseline: Ludic compiler + toolchain, Phase 1 syntax fixes complete	2026-08-27 15:15:35 +03:00
package.json	Baseline: Ludic compiler + toolchain, Phase 1 syntax fixes complete	2026-08-27 15:15:35 +03:00
README.md	feat(stdlib): namespaced standard library (issue #2 )	2026-08-30 00:26:19 +03:00

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 — where ludic-lsp lives. Empty = search bin/, then PATH.
ludic.server.enabled — turn the server off and keep only static highlighting.
ludic.compilerPath — where ludicc lives, 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