Yogthos 7167af4830 Trace by default in REPL-driven development ... A repl or nREPL session now turns tail-frame tracing on, so an uncaught error in evaluated/reloaded code shows a tail-frame backtrace with no JOLT_TRACE set. The REPL and nREPL catch errors themselves rather than going through the uncaught reporter, so they now print the history backtrace via a new jolt.host/backtrace- string (history-only — the live continuation in a REPL is just REPL machinery). Because the recording is baked in at compile time, only code compiled while a session is live is traced; reload a namespace to trace already-loaded code. JOLT_TRACE=1 still forces it on for a whole run (a plain -M:run traces its own load); JOLT_TRACE=0 forces it off even in a session. No seed change — jolt.main/jolt.nrepl are runtime-loaded and compile-eval.ss / source-registry.ss are host files.		2026-07-04 15:23:17 -04:00
..
clojure/core	Clojure 1.13 parity: req!, checked-keys destructuring, keyword array maps	2026-07-04 10:18:51 -04:00
jolt	Trace by default in REPL-driven development	2026-07-04 15:23:17 -04:00