I'll chime in with my opinion on this topic. I think the existing if-let and similar forms that have a limitation of only allowing a single binding is a confusing restriction to place on the familiar binding vector construct. I've always been a little uneasy about repurposing binding vectors for this restricted single-binding use case. I'd probably have preferred something more like as->, where there is a direct form binding pair. However I guess that would ruin the ability to destructure. Just a thought, I can live with if-let and it's slightly awkward binding vector though.
With that said, and as others have mentioned here, I can't imagine this proposed if-let-all macro having clear enough semantics to be something in Clojure core. There are just way too many caveats and ways to interpret it. I can see the motivation for it, but maybe there is a better design to achieve it. -- 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.
