Examples¶

The repository includes examples for language features and LOVE workflows.

examples/features¶

A buildable tour of the language and LSP features.

make build-features
make lsp-features-smoke

Use this when changing language-server behavior.

The feature tour opts out of the default standard lint set because several files demonstrate intentionally incomplete or suspicious patterns. Use the dedicated examples/linter fixture to exercise those rules.

The feature tour includes placeholder assets under src/assets/ so static LOVE asset validation, asset-path completion, and asset metadata hovers can run without depending on real art or audio files.

It also includes focused modules for the Baton-backed input({...}) helper, state machines, stores, Signals, ECS, object pools, sprite sheets, vectors, and Lua interoperability.

examples/linter¶

An intentionally failing diagnostic fixture with one named example for every currently emitted standard lint rule.

cargo build -p tua-cli
cd examples/linter
../../target/debug/tua lint

The lint command exits with status 1 by design. With standard rules enabled by default, tua check reports the same fixture warnings. The fixture has no tua.toml, so it does not participate in buildable-example or benchmark runs.

examples/love-minimal¶

A small LOVE project for basic compile-and-run validation.

make build-love-minimal
make run-love-minimal

examples/love-full¶

A larger LOVE conversion example with Lua interop.

make build-love-full
make run-love-full

The run target uses a smoke mode suitable for local validation.

examples/love-tua¶

A small playable bullet hell that combines Tua's ECS, object pool, store, state machine, and input helpers with a hand-written Lua projectile-pattern module and declaration-typed feel.lua feedback.

make check-love-tua
make run-love-tua

The .tua and .lua sources live together at the example root, including the tracked Feel runtime and declarations under lib/feel. Tua indexes the declarations without emitting them, copies runtime Lua unchanged, and writes the runnable project under the ignored build/ directory. Because the example is self-contained, it participates in the default example build and benchmark suites without network setup.

Syntax Validation¶

When LuaJIT or Lua is available:

make lua-syntax

The test skips gracefully when no compatible Lua executable is present.

LSP Benchmark Fixtures¶

benchmarks/lsp/small, benchmarks/lsp/medium, and benchmarks/lsp/large are checked-in Tua projects for profiling editor latency and cache behavior. They include comments describing the feature surface each file stresses. Larger deterministic fixtures are generated under target/ so 1,000 generated project files do not live in the repository.

make profile-lsp
make profile-completion
make completion-ranking-smoke
make generate-lsp-benchmarks
make profile-representative

Examples Speed Suite¶

The real bundled examples can also be profiled as a regression suite:

make benchmark-smoke
make profile-examples-smoke
make profile-examples
make profile-examples-baseline
make profile-all

The examples suite discovers every examples/*/tua.toml and times CLI commands and LSP editor requests. The representative suite measures generated large-file and project-scale fixtures, including request contention. Both write JSON reports under target/tua-speed/. The lint timing includes intentional warning fixtures; their documented diagnostic exit is measured rather than treated as a profiler failure. Check, formatting, build, process, and LSP failures still stop the suite. Example timing comparisons use local soft thresholds because timing varies by machine:

TUA_SPEED_BASELINE=target/tua-speed/examples-baseline.json make profile-examples