I'm not satisfied with the names for the new threading macros either. The new names being considered for let->, test-> and when-> are:
A) let-> becomes as-> reduces arg order and destructuring expectations. B) test-> becomes cond-> cond-> was the original name, and, protestations about not short-circuiting like cond notwithstanding, it is still the best fit. The doc string will say: "Note that, unlike cond branching, cond-> threading does not short circuit after the first true test expression." C) when-> becomes some-> and in doing so, tests for non-nil rather than truth. ========== This last one touches on the general area of non-nil-ness, often needed. Other possible (future) ideas in line with this are: (some? x) == (not (nil? x)) (some coll) ;;note no pred, == (some some? coll) this is tricky, as we are bridging CL's some and Maybe's Some if-some, when-some et al. (some! x) ;;(or somex ?) identity for all but nil, which throws etc ========== Last chance for fabulous and better names than these: (as->, cond-> and some->). Note that "cond-> doesn't match cond's short-circuit" has been considered already, please do not repeat. Thanks, Rich -- 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
