Pure functions are the building blocks of idiomatic Clojure(Script) programs, since we can easily understand and test them. By definition, these functions should not have any effects i.e. should not change the outside world. However, our programs are only useful if they produce effects like sending emails, displaying information, or saving information to databases.
This talk explores techniques for writing effects in ClojureScript. We’ll look at how to separate effects from pure functions, discuss the tradeoffs of tools like callbacks, Promises, and core.async, and explore some strategies for simplifying sequences of effects.
clj -A:client:rebel -m figwheel.main
- Terminal:
clj -A:client -J-Dclojure.server.repl="{:port 5555 :accept clojure.core.server/repl}" - Emacs:
M-x inf-clojure-connect - Choose localhost and 5555
- In Emacs REPL:
(require '[figwheel.main.api]) - In Emacs REPL:
(figwheel.main.api/start "dev") - In Emacs buffer (unless you already have
inf-clojureset to autoload):M-x inf-clojure-minor-mode
clj -A:server