Sorry I had completely forgotten about this post and just saw it now. I think this explanation makes sense although in most cases the thread value will also not be a function and if it is then it could be treated as invoking the threaded function's call and the result passed on to the next form.
On Sunday, January 27, 2019 at 5:23:24 AM UTC+5:30, Gary Fredericks wrote: > > There's probably also a difference in what happens if the form is empty. > The current impl results in a compile error about calling nil, whereas the > suggested implementation would result in calling the current thread value > as a function, I think. > > On Saturday, January 26, 2019 at 5:13:23 PM UTC-6, Sean Corfield wrote: >> >> I suspect it’s done for consistency with the source of -> (which has to >> use first/next because it threads the expression between them) – using >> first/next/x in ->> is therefore a closer parallel to using first/x/next in >> -> so it’s easier to see the similarity (and correctness) of the code. >> >> >> >> Sean Corfield -- (970) FOR-SEAN -- (904) 302-SEAN >> An Architect's View -- http://corfield.org/ >> >> "If you're not annoying somebody, you're not really alive." >> -- Margaret Atwood >> >> >> ------------------------------ >> *From:* clo...@googlegroups.com <clo...@googlegroups.com> on behalf of >> James Reeves <ja...@booleanknot.com> >> *Sent:* Saturday, January 26, 2019 11:08:25 AM >> *To:* clo...@googlegroups.com >> *Subject:* Re: Noob question on the --> macro implementation >> >> I believe he's just saying it's simpler and possibly more efficient. >> >> Unless I'm missing something subtle in the way this is resolved, I >> believe Ujjwal is right that: >> >> `(~(first form) ~@(next form) ~x) >> >> Is equivalent to: >> >> `(~@form ~x) >> >> On Sat, 26 Jan 2019 at 19:04, Andy Fingerhut <andy.fi...@gmail.com> >> wrote: >> >>> When you ask "am I right?" about your proposed change, what is it that >>> the current behavior does not do, that your change would do? Do you have >>> some use case in mind that works with your change, but doesn't with the >>> current implementation? >>> >>> Andy >>> >>> On Sat, Jan 26, 2019 at 10:50 AM Ujjwal Thaakar <ujjwal...@gmail.com> >>> wrote: >>> >>>> Hi, >>>> I'm trying to learn Clojure and I just curiously typed >>>> (source ->>) >>>> in the REPL and was wondering about this: >>>> https://github.com/clojure/clojure/commit/749a0ad8b66c781d8176833f0ad26cfe6b9b24e3#r32075784 >>>> >>>> Am I missing something? >>>> >>>> -- >>>> You received this message because you are subscribed to the Google >>>> Groups "Clojure" group. >>>> To post to this group, send email to clo...@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+u...@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+u...@googlegroups.com. >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Clojure" group. >>> To post to this group, send email to clo...@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+u...@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+u...@googlegroups.com. >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> >> -- >> James Reeves >> booleanknot.com >> >> -- >> You received this message because you are subscribed to the Google >> Groups "Clojure" group. >> To post to this group, send email to clo...@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+u...@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+u...@googlegroups.com. >> For more options, visit https://groups.google.com/d/optout. >> > -- 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.
