locking
(locking x body...)
Runs the body holding the lock of x and answers its last value. On the interpreter
and the JVM, where threads exist (a Ring handler runs one per request), the lock is a
reentrant mutex kept per value: by identity, a number by value, a keyword by its
spelling. Both wasm backends are single-threaded, so there the body runs as is. A nil
lock throws NullPointerException before the body. A recur in the body is refused,
like one inside a try.
(monitor-enter x) / (monitor-exit x) are the two halves of locking, holding and
releasing the same per-value mutex and answering nil. On the wasm backends the object
evaluates and nil answers. A nil object is the same NullPointerException.
Deviation: the lock table keeps every value it was handed for the program's lifetime,
and the NullPointerException message names the local locklocal where Clojure names
a generated one.