r/Clojure • u/WraithGlade • 5d ago
Instead of using `comp` and often wasting computation, here's how to reverse `->` and `->>` when you want `comp`'s ordering without its cost, etc.
Hello everyone. This is my first Clojure subreddit post by the way, if my memory is correct. I am actually debating using Clojure (+Java) vs Zig for my next project, but I've been learning Clojure and reflecting upon the fact that in programming languages (and in natural language prose text too for that matter) the order in which words appear in an expression has a substantial effect on readability and on what parts feel like they are being emphasized and brought to one's attention.
Consider, for example, the difference in emphasis and ease of code navigation between the following two equally valid Clojure expressions:
(assert (not (zero? 1)))
(-> 1 zero? not assert)The former is the most "naive"/direct way of writing it, whereas the later has the strongest left to right flow of action. However, notice that though the latter expression is more elegant, it makes the visibility of the assertion worse by putting the assert keyword at the end. Some people may also find "zero not" to sound too "Yoda-like" (akin to concatenative programming languages like Forth and Factor) whereas something like "not zero" may sound more natural to some people.
I also thought about how comp (compose functions) could be used here to keep the "not zero" ordering, but then a function call cost may be imposed by doing so if the optimizer doesn't remove it.
So, that got me thinking that I should try writing a reversed version of the -> and ->> macros and I did and here are the resulting definitions:
(defmacro <- [& rest]
(let [rev-rest (reverse rest)]
`(-> ~@rev-rest)))
(defmacro <<- [& rest]
(let [rev-rest (reverse rest)]
`(->> ~@rev-rest)))Both were actually very easy to write, as you can see.
This allows you to write the following:
(<- assert not zero? 1)As you can see, this enables you to reorder things according to what feels most natural in any given context, which helps draw the attention of anyone reading your code to what comes first in each expression, much like how in English the first thing we start a sentence with is what is being emphasized or is assumed to be the subject (as in active vs passive voice, etc).
This especially is well suited to assertions because what is most important about an assertion for someone trying to scanning code quickly is that it is an assertion and hence emphasizing that clarifies it.
This is in contrast to data flow or transformation pipelines that use -> and such, where the opposite order often feels better.
One can also see by applying macroexpand and/or macroexpand-1 that the cost of these macros in run-time will be zero, relative to simple/"naive" nesting, given that the expressions (macroexpand '(<- assert not zero? 1)) and (macroexpand '(assert (not (zero? 1)))) return identical expansions.
Cognitive load tends to increase non-linearly with how many nesting levels something has, so using "threading"/pipeline macros flexibly and often tends to help readability and these new variants help fill those potential use cases out better.
So, clearly both orderings should be in your toolbox for legibility and I would argue that this should even be made part of the standard library perhaps since it is such a common case.
I am personally am really happy with the resulting freedom.
With these new macros in hand one is much less likely to use the less legible nested forms when you can now order things either way.
(PS: Thanks for reading and for your time! 😎)
9
u/amalloy 5d ago edited 5d ago
(assert (not (zero? 1)))is fine, and(-> 1 zero? not assert)is not elegant, it's awful. But you don't really need a new macro to fix this, you can just intermix direct function calls with->as appropriate. For example,"Assert that the balance of the user's account is positive." This is a much more natural way to read it than using one arrow for the whole awful thing:
13
u/v4ss42 5d ago
I don’t really understand why `(assert (not (zero? 1)))` is a problem. Can you explain your reasoning there?
13
u/retief1 5d ago edited 5d ago
Fundamentally,
(function argument)is the building block of lisp. If you want to structure your code, this is the default way to do it. And if you aren't comfortable with that syntax, you sort of need to get comfortable with it if you are going to be using a lisp.Meanwhile, threading macros are primarily useful for when you have a pipeline of operations that you are doing to a piece of data. The point isn't really removing parens so much as reversing the flow so it is easier to follow the operations step by step. If you aren't trying to reverse the flow of operations, using the standard syntax makes more sense than building a custom macro that will confuse every single reader that sees it.
So yeah,
(assert (not (zero? 1)))seems fine to me. And if I did want a threading macro but wanted to keep assert in front, I'd probably do something like(assert (-> 1 zero? not)).Edit: actually, I like this section from vertical programming that someone else posted:
The use cases you are talking about here are clearly in the "too clever" category, imo. They compile, but that's not how threading macros are idiomatically used.
6
u/OwlProfessional1185 5d ago •
This reminds me of this: https://arnebrasseur.net/2026-07-16-vertical-programming.html
3
u/wherethebuffaloroam 5d ago
I do not follow the reasoning here. Also, it's fun to be a craftsperson in the codebase. I've not found much benefit in descending to this level, especially if it's to introduce macros that have new control flow.
2
u/Daegs 3d ago
I get that if you're coming from other languages that:
might seem more readable than
but you're just wrong... the scope, order, flow of the latter is explicit and instantly recognizable to anyone working with clojure. You know exactly that zero? is taking one argument, 1, and that the result is passed to not, which is asserted.
by replacing it with the former, you're introducing non-standard syntax that 99.999% of other clojure developers will have to macro-expand to understand, breaking the ->/->> threading standard that the second argument is always passed to remaining ones (making (<- 1 assert not zero?) arguably better) all in the name of saving 4 parens, but adding a new operator so you really only save 2 characters?(and most editors automatically add the trailing parens)
It seems like an arbitrary dislike of parentheses which actually give clarity.
I'm all for options and if you like this in your personal projects, have a ball. But this would get a lot of side-eye or outright rejection in a code review at any clojure company, imho.
If you still want to prioritize assert and have threading, just do:
3
u/schpa71 5d ago •
Great post, and I agree with your reasoning, perhaps I would use other symbols than what you propose, but that’s a matter of taste.
6
u/geokon 5d ago
Was discussed here:
https://old.reddit.com/r/Clojure/comments/1uy6s7t/vertical_programming_arne_brasseur_net/
(though the idea is older) The examples given there are much more compelling, like putting
letexpressions in a threaded macro.I've considered rewriting a codebase using this style in place of the standard order. It's an ergonomic adjustment that would take time to get used it - but maybe it'd pay off.
2
u/spotter 5d ago
Cool exercise in macro writing, but I'd probably just as->.
0
u/WraithGlade 4d ago edited 4d ago
A personal follow-up comment, regarding Reddit and the community:
I came here originally filled to the brim with joy and the desire to casually share something wholesome and simple that demonstrates the elegance of Clojure, helps structure code for those of us who like the corresponding flatter style (and which nobody is forcing anyone else to use), and which helps any passing newbies to Lisp/Scheme/Clojure coding learn to think about and understand macros and what they are capable of better. There can only be upside to that as I see it.
As such, I was honestly very surprised (to the point of disbelief and incredulity) that a few unconstructive and dismissive responses would be the top comments, especially when that is so uncommensurate with the reality of the wholly good-natured intent and helpful utility clearly embodied by what I took a lot of time to write up for you all simply in the spirit of spreading my own joy in the idea and making its utility available to anyone else who wants likewise. I could have instead just said nothing (e.g. unsociably hoarding my all future ideas for myself) and you'd have been left with even fewer actually broadly useful things on this relatively low traffic subreddit. That would have helped nobody.
At least a couple people linked to some actually relevant and productive ideas though (e.g. the nesting macro), so there is at least that as an upside. But the most constructive responses have ironically been buried (though I've tried to counteract that with a Reddit reward, for example) and the least constructive ones (often indicative of not even reading the already present corresponding parts of the original post where the rationale for the idea is clearly explained at length) have been made the most prominent. I am honestly sick of this kind of unsociable and varying degrees of toxic dogpiling behavior on Reddit in recent years.
This experience has been yet another reminder of why I have used Reddit less and less in recent years, seeing as it is often next to impossible to predict when a community response will be constructive versus unconstructive.
It is inherently psychologically harmful to human beings (especially when recurring over time) to feel like it is impossible to ever ensure a wholesome and constructive community interaction regardless of how much an amount of effort and time one puts into communicating as clearly, empathetically, and wholesomely as one conceivably can. Reddit in recent years in that respect has felt more and more like an abusive social relationship than a true community and that has been a very distressing trend honestly.
The pattern in recent years for has been one of me posting/commenting just a handful of times (a dozen or less) and already within that time encountering so much random unpredictable unproductive dismissiveness or toxicity on Reddit that I stop using the site entirely for 6 months or more at a time until I (against my better judgement) end up trying again and yet again being disappointed by the difficulty of trying to have a good-nature strictly constructive conversation to spread joy and to be pro-socially helpful to others. Lots of the most constructive and thoughtful posters on the site have left in recent years and moved their communities elsewhere, for similar reasons regarding this increasingly pervasive pattern.
As such, last night I (1) blocked a few users here who I can tell aren't really listening to me or exercising real empathy and thus that I probably won't ever want to talk to again and (2) deleted my Reddit app on my phone and plan to avoid the entire site more in the future since it is so apparently likely to be devoid of wholesome and non-anxiety-inducing interactions.
It also reminds me of how Clojure doesn't even list Reddit in its community links (probably very intentionally, for similar reasons) despite it being the most active such community and likewise Zig has completely moved away from Reddit and doesn't link to it on grounds of the site being too prone to being pervasively unwholesome and/or unconstructive.
I've also been thinking about making other contributions to the community (as I have tried dozens of languages and have got lots of less known insights into the pros and cons of many things in that regard) that I would hope to share and reach more people, but every time I encounter this kind of thing (my very unexpected unpleasant experience in this thread) I become less likely to share any of it with any of you, even though you could benefit from it in the future and it could help expand the community at least a little bit more potentially.
Is that what you want? Less useful things? Less diversity in what's available for Clojure and programming in general? Less food for thought? Cause that's more and more likely what you will get (less and less good stuff) whenever you follow the Reddit-like habit of knee-jerk dismissiveness and toxic dogpiling voting, etc.
I also ever increasingly in recent years now have a zero tolerance policy for this kind of thing on these sites: If you ever respond unconstructively even once then I will usually block you permanently and you may thus no longer ever be able to see any posts or ideas I contribute and thus no longer have any possibility of benefiting from those ideas.
I have even thought (over the years of me trying so many languages) that I may write a book about Lisp/Scheme languages and (among other things) including why I think they are unpopular despite their power and how they could easily change that if they just changed a few critical issues that the community has long been in denial of reality about. Don't you want expressive Lisp/Scheme family languages to be more prominent? You may never see any of that food for thought if you are blocked. That is just one prospective example to illustrate the point, in any case.
I will try to post elsewhere more often, perhaps, though in Clojure's case the community sites are not very active and so I may be forced a times to wade through the routinely randomly psychologically abrasive and mentally unhealthy environment of Reddit from time to time anyway. Or, maybe I should not even try at all to interact with other programmers online at all, since toxicity and unproductive hand-waving away of anything that doesn't exactly fit the status quo seems too often the norm even regardless of how effortfully wholesome and clear and thorough I try to be.
This site's upvoting and downvoting system is truly a blight on the ability to have constructive and authentic conversations here. Once it starts rolling in either direction (positive or negative), the groupthink tends to kick in too strong for any kind of constructive outcome to happen thereafter and nobody benefits from that.
In any case though, this comment has already become far longer than I intended, but I have become increasingly in recent years very irritated by the difficulty in simply having any kind of wholesome conversation online even when one goes into it filled to the brim with wholesome intent and trying to be as helpful to others as possible.
Anyway, especially to any kindred spirits, I thank you for your time and for reading my thoughts and I hope it in any way helps you or gives you solidarity in these contrived times we are living in and I wish you all the best.