do’s and don’ts – Digital Digressions by Stuart Sierra
Continuing my series of Clojure do’s and don’ts — which, as always, is a mix of technical recommendations and my personal stylistic preferences — and continuing on the topic of the previous post in this series, here are some more arbitrary rules about anonymous functions.
Continuing my series of Clojure do’s and don’ts — which, as always, is a mix of technical recommendations and my personal stylistic preferences — and continuing on the topic of the previous post in this series, here are some more arbitrary rules about anonymous functions. A mistake that shows up at least once in almost every class I teach. The Clojure reader macro #() creates an anonymous function whose body is a single expression, and that expression must be a list. A brief addendum to my last post about Clojure’s threading macros. As I was saying … I said you could use as-> to work…
saved by
related reading
- The Clojure Style Guideguide.clojure.style
- Good examples of Clojure macros usage which demonstrate advantages of the language over the mainstream? - Stack Overflowstackoverflow.com
- My Clojure Workflow, Reloadedcognitect.com
- Clean Coder Blogblog.cleancoder.com
- Val on Programming: What makes a good REPL?vvvvalvalval.github.io
- Radarjuxt.pro
- Notes on structured concurrency, or: Go statement considered harmful - njs blogvorpus.org
- Essays on programming I think about a lot | benkuhn.netbenkuhn.net
- CSC 151 - Anonymous procedureseikmeier.sites.grinnell.edu
- A half-hour to learn Rustfasterthanli.me
- Some thoughts on writingdanluu.com
- An introduction to functional programmingcodewords.recurse.com