Docs / Quidra 0.3.0
Documentation
Quidra's reference documentation lives beside the compiler in the quidra-lang/quidra repository, where its examples are verified by the compiler's own test suite. This page is the map.
Language
- docs/spec/language.md Language semantics The normative description of Quidra: types, bindings and definite initialization, functions, classes, generics, references and const authority, unions and match, tensors and device placement, standard namespaces, neural values and the C FFI.
- docs/spec/grammar.ebnf Grammar The EBNF grammar of Quidra source, including the lexical constraints on numeric and string literals and the static constraints the frontend enforces.
- docs/spec/numeric-and-bin.md Numeric types and bin Fixed-width integers, floating-point types, exact bigint and bigreal, explicit conversion rules, fixed-width bitwise operators and the packed binary type bin.
Working with the compiler
- docs/spec/llm-guide.md LLM guide The canonical generation rules for writing Quidra, for language models and people alike: numbered rules on what to write and what not to invent, a complete example and the verification commands.
- docs/spec/diagnostics.md Diagnostics Every compiler diagnostic code with its meaning and typical correction, the JSON output of quidra check, and the deterministic runtime safety failures.
- docs/spec/patch-schema.md Source patch schema The revision- and hash-checked structural patch format consumed by quidra patch, for tools that edit programs as checked transactions rather than text.
- docs/spec/architecture.md Architecture How the compiler is built: phases and lowering invariants, core contracts, format versions, the WebAssembly frontend boundary and the native runtime boundary.
Project
- docs/packages.md Package management Installing released packages from immutable tags, the quidra.package manifest, project.toml metadata, lockfiles and local development packages.
- docs/development.md Development and release workflow Branch roles, versioning, the single source of truth for project metadata, the core release procedure and how first-party libraries are released after it.
- examples/ Examples Small complete programs kept in the compiler repository and exercised by its test suite.
- README.md README The design thesis, the design laws derived from semantic compression, the build instructions and the CLI reference, in one document.
Machine-readable
The compiler documents itself
quidra describe prints the language and tooling contracts as JSON: the compilation pipeline, the
current types and built-ins, the specification documents and the format versions. The grammar, the patch schema
and the LLM guide are available the same way.
quidra describe
quidra describe grammar
quidra describe patch-schema
quidra describe llm