/tags/clojure/Recent content in clojure on Azrea AmisHugo -- gohugo.ioen-usThis work is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License.Sun, 15 Dec 2019 23:01:08 +0100/posts/2019/12/15/interesting-clojure-macro-interaction/Sun, 15 Dec 2019 23:01:08 +0100/posts/2019/12/15/interesting-clojure-macro-interaction/Clojure’s macro system is a little tricky to work with (at least for me), but it’s also quite powerful. Being able to rewrite the languages AST at compile time is really cool, and the fact that Clojure’s syntax is just the data structures that normal Clojure code operate on makes writing macros a breeze (at least compared to, say, Rust or Javascript). Clojure’s macro expansion works in dependable way: it keeps apply macros until there are no more macro calls in the code, then compiles the resulting code./posts/2019/05/30/clojures-looping-syntax-is-surprising/Thu, 30 May 2019 11:52:59 -0700/posts/2019/05/30/clojures-looping-syntax-is-surprising/They aren’t super popular, but Clojure has a rich set of high level looping macros. You have for for list comprehensions, doseq for imperative looping over sequences, dotimes for an even simpler integer loop, while for raw predicate looping, and loop for any kind of arbitrary recursion-style looping you want to do. However, I’m not a huge fan of the exact syntax some of these macros use. Let’s talk about let, which looks like this:/posts/2019/05/28/codegen-loader/Tue, 28 May 2019 17:04:04 -0700/posts/2019/05/28/codegen-loader/In what is very likely an enormously bad idea, I have built a JVM classloader that can load dynamically load Java source files into memory. Why I’ve recently been going “Full Juxt”, using all of Juxt’s Clojure libraries, specifically juxt/aero for configuration, juxt/bidi for routing, juxt/yada for endpoint handling, weavejester/integrant for “building applications” (probably dependency injection), juxt/joplin for database migrations, and juxt/edge to tie it all together. All of Juxt’s libraries are relentlessly data focused, and use deps./posts/2018/11/03/pipeline-operators/Sat, 03 Nov 2018 19:28:01 -0700/posts/2018/11/03/pipeline-operators/Pipeline “operators” or “threading”1 constructs are interesting language constructs. They are an acknowledgement that functional code can be a little obtuse. They reorient (or rewrite) functional code so it looks more like a “dataflow”. Particularly of Lisps, but also of some other functional languages, execution moves from the inside of expressions to the outside in a way that’s not particularly natural feeling. It’s a real source of the difficulty people express when reading functional code./posts/2018/08/15/operators/Wed, 15 Aug 2018 16:21:39 -0700/posts/2018/08/15/operators/I recently started thinking about operators and math in programming languages. This is at least partly inspired by the programming language I’m making right now, but I’ll get to that later. It’s also inspired, in some sense, by the tutorials I was reading while trying to successfully parse my programming language. I didn’t find a tutorial specifically for what I was trying to do, which was fair, but I did find tutorials on parsing other more “normal” languages or more C-like languages, and it got me thinking.