Recipes: each namespace below demonstrates one shape of async eval
against this system, as real code — loaded with the library, so a
recipe that stops compiling breaks the load rather than quietly
rotting. (__r/nses "patterns") is the index; outline a recipe
namespace for its signatures and docstrings; file it for the
(comment …) walkthroughs, which is where eval-by-eval choreography
lives. Walkthrough code is eval code: it assumes the scratch
refers (qlet, qfor, …) and the __r/__q aliases, like any
eval. These namespaces speak the tooling spelling throughout — __q,
the alias your evals carry everywhere — not the q of committed user
code, which is yours to require in source you own. House discipline:
defns and comment blocks only, nothing effectful at the top level —
these namespaces load inside the host JVM at boot, so loading must be
inert.
Recipes: each namespace below demonstrates one shape of async eval against this system, as real code — loaded with the library, so a recipe that stops compiling breaks the load rather than quietly rotting. `(__r/nses "patterns")` is the index; `outline` a recipe namespace for its signatures and docstrings; `file` it for the `(comment …)` walkthroughs, which is where eval-by-eval choreography lives. Walkthrough code is *eval* code: it assumes the scratch refers (`qlet`, `qfor`, …) and the `__r`/`__q` aliases, like any eval. These namespaces speak the tooling spelling throughout — `__q`, the alias your evals carry everywhere — not the `q` of committed user code, which is yours to require in source you own. House discipline: defns and comment blocks only, nothing effectful at the top level — these namespaces load inside the host JVM at boot, so loading must be inert.
No vars found in this namespace.
cljdoc builds & hosts documentation for Clojure/Script libraries
| Ctrl+k | Jump to recent docs |
| ← | Move to previous article |
| → | Move to next article |
| Ctrl+/ | Jump to the search field |