Hi, "Whenever you notice this pattern, you can probably turn to one of the > threading macros instead." > > that would fly in the face of being more declarative; when we start to > put in explicit ordering, instead of leaving it as just relationships, > that can be bad. of course it can also be good. even both at the same > time. > at least in this example, ordering is required for the operations to produce the correct result, so I would say it for good
cheers, -Gianluca -- 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.
