3 ms·
It's a naming trick. It's not "impure" code, it's locally state-modifying, which looks impure inside a limited context, but the changes can't leak beyond a defi
by gowld 9y ago
It's a naming trick. It's not "impure" code, it's locally state-modifying, which looks impure inside a limited context, but the changes can't leak beyond a defined boundary. In Clojure this is called "transient", and it's much better explained there, because Rich Hickey believes programming should be comprehensible: https://clojure.org/reference/transients https://clojure.org/reference/transients