Date: 2026-06-16
The contract could try to describe how Zig computes, or only what crosses the boundary.
The Clojure signature describes only inputs, outputs, ownership, and lifetime at the boundary.
Zig stays free to use allocators, comptime, pointers, packed structs, SIMD, C imports, and target-specific optimization internally; the Clojure side never tries to model these.
Modeling Zig internals on the Clojure side was the thing to avoid; it would couple the two languages and weaken Zig's freedom for no gain.
Can you improve this documentation?Edit on GitHub
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 |