jolt modelled letfn as a special form directly, so (macroexpand-1 '(letfn …)) returned the form unchanged. Clojure's letfn is a macro that expands to letfn*, and macroexpansion tooling (tools.macro, tools.analyzer) depends on that — its special-form handlers key on letfn*, not letfn. Split it the Clojure way: - letfn* is now the special form (analyzer), taking flat name/fn-form pairs [name1 fn1 name2 fn2 …] — the letrec :let lowering is unchanged. - letfn is a macro (00-syntax) turning each (name [params] body*) spec into a name + (fn name [params] body*) binding, so it expands to letfn*. So (macroexpand-1 '(letfn [(f [x] x)] (f 1))) now yields (letfn* [f (fn f [x] x)] (f 1)), and clojure.tools.macro passes its whole suite (macrolet / symbol-macrolet / mexpand-all). Listed in docs + site. make test green (+1 corpus row, 0 new divergences), shakesmoke byte-identical. One re-mint (analyzer + the letfn macro); selfhost holds.
4.7 KiB
4.7 KiB
Clojure libraries known to work with Jolt
Libraries confirmed to load and pass their conformance checks on Jolt. A library listed here works. See the examples, e.g. the ring-app example.
- aero — EDN configuration with tag literals
(
#ref/#env/#or/#profile/#long/…) - config — environment configuration
- Selmer — Django-style templates
- medley — collection utilities
- cuerdas — string manipulation
- ring-core — via
:deps/root "ring-core", on the ring-app example - ring-codec — URL/form encoding
- ring-defaults — the standard middleware stack (params, static resources + content-type, session, security headers); its session/CSRF crypto comes from jolt-lang/jolt-crypto (OpenSSL)
- reitit-core — data-driven routing; the
reitit.TrieJava class is mirrored by jolt-lang/router. - integrant — data-driven system
configuration (
#ig/ref), with its dependency and meta-merge deps - honeysql — SQL formatter and helpers
- clojure.jdbc — as
jolt-lang/db's
jdbc.core, over the built-in SQLite access (libsqlite3 via Chez's FFI) - next.jdbc — a compatibility layer in
jolt-lang/db over
jdbc.core - tools.logging — runs verbatim over a
native
clojure.tools.logging.implstderr backend - migratus — database migrations over the next.jdbc layer
- malli — data schema validation, on the malli-app example.
- markdown-clj — Markdown → HTML, on the markdown-app example
- hiccup — HTML from Clojure data, on the hiccup-app example
- clojure.data.json — JSON reading and writing
- clojure.spec.alpha — data specs
- core.match — pattern matching.
- core.cache — caching (Basic/FIFO/LRU/ LU/TTL/Soft + the wrapped atom API), over data.priority-map.
- core.memoize — function memoization over core.cache.
- core.async — CSP channels and
goblocks (<!/>!/alts!,pipeline,mult/mix/pub/sub) on real OS threads. - core.logic — relational logic programming
(unification,
run/fresh/conde, finite domains). - math.combinatorics — permutations, combinations, subsets, selections, cartesian products, partitions.
- core.contracts — programming by
contract (
contract/with-constraints/provide), over core.unify. - data.zip — zipper navigation, including
clojure.data.zip.xml; XML parsing via jolt-lang/xml (which now shipsclojure.xml/parse). - data.csv — reading and writing CSV.
- data.codec — base64 encode/decode over byte arrays.
- data.priority-map — priority
maps (incl. keyfn / custom comparator), with
subseq/rsubseq. - tools.macro — local macros
(
macrolet/symbol-macrolet),mexpand/mexpand-all. - test.check — property-based testing
(generators,
quick-check, shrinking). - tick — date/time over Jolt's
java.time;#time/…literals viatime-literals. - transit-jolt — Transit (JSON) read/write