I've needed --> a few times in my code. I don't think I need it as much as just -> or ->>. Most of the time I've needed it is because I or someone else essentially had parameters in the wrong order. Maybe it belongs in contrib along with -?> which I've needed sparingly as well, but have found useful and would've been non-trivial to have conjured.
On Jul 6, 5:22 pm, David Nolen <dnolen.li...@gmail.com> wrote: > On Tue, Jul 6, 2010 at 5:02 PM, Greg <g...@kinostudios.com> wrote: > > > I'll make a list here of the reasons given for Yay/Nay so far: > > > Nay: > > > 1) "I haven't had a need for a general threading macro." > > 2) The response so far is negative (and consists of repeating point #1 > > above). > > 3) It would encourage people to not follow Clojure's conventions around > argument positions for fns that deal with sequences/collections. > > That is a pretty important Nay and illustrates that --> decreases > readability for people that have spent time with Clojure. > > It also points out why -> and ->> are not really about position anyway, it's > about threading an expression. -> is to make Clojure read left-right instead > of inside-out. ->> is to make Clojure read left-right when operating on > sequences/collections. > > Both are far, far more common and useful then being able to fill arguments > anywhere. > > David -- 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
