The way you explained trailing closures in this made something finally click in my brain! I have no idea how it was able to confuse me for so long - it’s just so simple. Thank you!
Finally this video clicked for me... Simple examples makes you understand... i have watched 3 other videos across UA-cam to understand high order functions but they had stupid azz examples i couldn't understand a freking thing...
cool vid, but I believe that $0 and $1 when reducing does not refer to "this and next iteration", but to "current result and current iteration" - isn't that right? :) because here you keep handling constantly "accumulating current result" with each collection's element.
Yes that is how I understood reduce, even in other languages. It would accumulate - add the first and second, then add the third to that value. I think of $0 meaning lhs (left hand side) and $1 rhs
@@Jacob-rm7vo exactly. Filter iterates through the array, doing this: sumSoFar += object.numberToAdd So $0 is the lhs, and $1 is the object on the rhs. This is why Sean needs to write $1.users and not $0.users. $0 is an Int already.
Great explanations, really appreciate it. A few reactions if you're open to such things: 1. Using Double for currency values will work 99.99% of the time. It's that .01% that will drive you crazy. 2. I wouldn't use the for loop as a tool to explain filter/map/reduce. Your original explanation is great and more than sufficient. Adding discussion of the for loop way of calculating will confuse a certain percent of viewers, and slow down almost everyone.
I disagree. He’s right in bringing up the for loop for comparisons, since that is the whole point on declarative programming: streamline the uglier, more verbose imperative style
The way you explained trailing closures in this made something finally click in my brain! I have no idea how it was able to confuse me for so long - it’s just so simple. Thank you!
I remember that feeling! Happy to help.
Excellent video . Thank you Sean .
Glad you enjoyed it
Finally this video clicked for me... Simple examples makes you understand... i have watched 3 other videos across UA-cam to understand high order functions but they had stupid azz examples i couldn't understand a freking thing...
Glad it finally clicked!
Big Love Sean, THANK YOU, you and Afraz are the best
smart explanation, clear language! very efficient.. very.. ! 👏🏻
Thanks for the shares. You have many followers from Turkey. Even though I watch with automatic subtitles, I learn a lot.
Never knew about a reduce, just learned it today. Thanks, sean. I've been doing it the hard way all this time.
Thank you so much for putting this together! Especially for map and reduce!
Excellent explanation, as usual. Thank you!
thank you!
Great explanations for these
You can use keypaths with these high level functions. Makes for great readability!
Great job Sean, before this I really got stuck which one is
Amazing you are the best,Thanks for being one of the best is swift 👍
Thanks for the kind words, Ahmed.
Cool video. Learned some new things today. Thank you!
Amazing !
Thanks
How about Zip? How does it work and when is useful?
Thanks.
Happy to help!
cool vid, but I believe that $0 and $1 when reducing does not refer to "this and next iteration", but to "current result and current iteration" - isn't that right? :) because here you keep handling constantly "accumulating current result" with each collection's element.
Yes that is how I understood reduce, even in other languages. It would accumulate - add the first and second, then add the third to that value. I think of $0 meaning lhs (left hand side) and $1 rhs
@@Jacob-rm7vo exactly. Filter iterates through the array, doing this:
sumSoFar += object.numberToAdd
So $0 is the lhs, and $1 is the object on the rhs. This is why Sean needs to write $1.users and not $0.users. $0 is an Int already.
Thanks Sean!!
Great explanations, really appreciate it.
A few reactions if you're open to such things:
1. Using Double for currency values will work 99.99% of the time. It's that .01% that will drive you crazy.
2. I wouldn't use the for loop as a tool to explain filter/map/reduce. Your original explanation is great and more than sufficient. Adding discussion of the for loop way of calculating will confuse a certain percent of viewers, and slow down almost everyone.
I disagree. He’s right in bringing up the for loop for comparisons, since that is the whole point on declarative programming: streamline the uglier, more verbose imperative style
Awesome 🎉
Is there any plan for portfolio review? I’d love to hear your opinion about my website.
Thank you in advance 😊
Thanks!)
nice
69th like