Re: Strange update-in Behavior

2014-05-29 Thread Stuart Fehr
Ah, for some reason, I had it in my head that the value found in the map was the *last* argument passed to the function. This behavior makes a lot more sense now. Thanks for the clarification! On Thursday, May 29, 2014 11:00:58 AM UTC-6, Stuart Fehr wrote: > > I am not sure if this is considered

Re: Strange update-in Behavior

2014-05-29 Thread Ben Wolfson
it is expected behavior, because update-in calls the supplied function with the value it finds in the map as the first argument, so your first call ends up being (remove [1 2 3] #{2}) Since ([1 2 3] 2) = 3 and is truthy, the result is (). In your second case you're using (partial remove #{2}), s