5f72ec9bcb
Spec coverage dashboard had 6 missing-portable and 24 dynamic-var entries. The portable ones are now implemented (missing-portable -> 0, dynamic-var -> 14): - Stateful matcher: re-matcher now returns a real mutable Matcher; re-find over it steps through matches and re-groups returns the last match's groups (was an inert tagged map). Closes re-groups. - letfn is interned as a clojure.core var so (resolve 'letfn) matches the JVM. It stays a special form (the value is never invoked, not marked a macro). - *1 *2 *3 *e interned (nil outside a REPL). - Portable dynamic vars whose default already matches jolt's behaviour: *read-eval* *print-dup* *print-namespace-maps* *flush-on-newline* *compile-files* *math-context* *command-line-args* *file*. The remaining 14 dynamic-var entries are host-internal (compile-path, compiler-options, fn-loader, reader-resolver, repl, source-path, ...) or deferred pending printer/reader support (*print-length* *print-level* *default-data-reader-fn*). Corpus rows added for each closed gap; coverage.md regenerated. |
||
|---|---|---|
| .. | ||
| 00-front-matter.md | ||
| 02-reader.md | ||
| 03-special-forms.md | ||
| 09-core-library.md | ||
| coverage.md | ||
| README.md | ||
The Clojure Language Specification (Draft)
A normative, implementation-independent specification of the Clojure
language, developed alongside jolt's self-hosted compiler and validated by
its executable conformance suites. Why: Clojure has no spec — every
alternative implementation re-derives semantics from the reference
implementation and folklore. See the RFC for motivation, scope, evidence
sources, and process: ../rfc/0001-language-specification.md.
Documents
| Doc | Content | Status |
|---|---|---|
00-front-matter.md |
conformance terms, entry format, host classification | drafted |
02-reader.md |
token grammar + reader-macro catalog | drafted |
01, 04–08 |
see chapter plan in front matter | planned |
03-special-forms.md |
special-form catalog + normative exemplars (if, let*) |
exemplars |
09-core-library.md |
per-var entry format + exemplars (first, reduce, parse-uuid) |
exemplars |
coverage.md |
generated dashboard over the 694-var surface | generated |
../grammar.ebnf |
reader surface syntax (EBNF), companion to 02-reader.md |
reference |
Regenerate the dashboard after surface changes:
python3 tools/spec_coverage.py (reads tools/clojuredocs-export.json and
probes a working jolt checkout via bin/joltc).
Current numbers (2026-06-22)
Of the 694 clojure.core vars in the ClojureDocs inventory, jolt interns 574.
Broadly:
- 568 implemented in jolt and exercised by the behavioral suites
- 6 implemented but not directly tested — each gets a test with its spec entry
- 6 portable but absent from jolt's resolvable surface (the REPL history
vars
*1/*2/*3/*e, plusletfn/re-groups, which work but aren't interned whereresolvecan see them) — tracked as gaps - the rest classified host/JVM/concurrency (see the dashboard for the full per-var breakdown — it is the source of truth)
How this connects to the test suites
test/chez/corpus.edn— the host-neutral behavioral corpus, one row per case ({:suite :label :expected :actual}). The Chez compiler evaluates each case viahost/chez/run-corpus.ss(run withmake corpus), andtest/conformance/certify.cljcertifies every:expectedagainst reference JVM Clojure (run withmake certify). Spec entries cite these cases.test/conformance/— the certification tooling and classified divergences (certify.clj,known-divergences.edn); see itsREADME.mdandSPEC.md.vendor/clojure-test-suite— the cross-dialect suite (≥4081 assertions passing); dialect splits there are classification evidence.- jank's per-construct corpus (
~/src/jank/compiler+runtime/test/jank) is the granularity model for §2/§3 conformance.
The invariant: every numbered normative statement names its conformance test, or is marked UNVERIFIED. The spec cannot drift from the implementations that check it.