Completed
Details
Assignee
Stuart HallowayStuart HallowayReporter
gfredericksgfredericksApproval
OkPatch
Code and TestPriority
MinorAffects versions
Fix versions
Details
Details
Assignee
Stuart Halloway
Stuart HallowayReporter
gfredericks
gfredericksApproval
Ok
Patch
Code and Test
Priority
Affects versions
Fix versions
Created December 7, 2012 at 2:28 AM
Updated August 15, 2013 at 12:13 AM
Resolved August 15, 2013 at 12:13 AM
My intuitive understanding of the classic threading macros is that the meaning of forms like
(-> a b c)
can be understood syntactically independent of the meaning of the symbols involved or the fact that the two threading macros are defined recursively. However the recursive definition breaks that expectation. Afterc
is now in control if it is a macro, and is now seeing the argument(-> a b)
rather than(b a)
as would be the case if we had written(c (b a))
originally.Admittedly I do not know of a realistic example where this is an important distinction (I noticed this when playing with a rather perverse use of
->>
with macros from korma), but at the very least it means that the behavior of the threading macros isn't quite as easy to accurately explain as I thought it was.