comp isn't backwards, it's just "outside-in". ((comp not zero?) x) == (not (zero x))
So it reads in the same order from left-to-right as it would otherwise. On Friday, October 2, 2015 at 1:10:54 PM UTC-6, Jason Felice wrote: > > Why is it so hard to describe to new people? > > I mean, the questions I get are (I understand what's happening here, but I > can't describe it well): > > 1. If -> threads things first-to-last, why does the middleware run > last-to-first? > 2. Why is comp backwards? > 3. Wait, so how does each wrapper get a second pass at it? > 4. Why would you do this to me? > > I hope to write a blog or something on this, but I wanted to check in here > first. Any ideas on how to talk about this? > > Thanks, > -Jason > -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
