Hi @Paul Hudson, I'm trying to understand the logic behind setting the function to return a Boolean in the beginning. In order to get the result we are looking for, could we not just define the function with the other two blocks of code at the bottom, skipping the Boolean definition?
Yes, I love it when he slows down a bit. Also, what is the point of 60 seconds tutorials, I am fine with 3-minute ones. I briefly went to online Lambda school and their lectures are at least 3 hours long each time. Anyways, the point that he is making in this video and some would struggle is - he calls a function from another "if" function by giving it a parameter. That's a tricky one.Basically, by giving a parameter (name: "Red") , he activates a function above that function. You can see it better if you use Xcode
Watch next: Introduction to Swift: Optionals - ruclips.net/video/OkzZ3T3lrlg/видео.html
Questions? Comments? Tweet me @twostraws.
Hi @Paul Hudson, I'm trying to understand the logic behind setting the function to return a Boolean in the beginning. In order to get the result we are looking for, could we not just define the function with the other two blocks of code at the bottom, skipping the Boolean definition?
U manage to find the answer yet?
You can slow down and speed up the videos on youtube. Just in case you did not know 😉
I love your tutorials, but for me you are talking and explaining too fast. Thank you for your free videos!
I'm sorry that no one got your Taylor Swift Fearless pun
Yes, I love it when he slows down a bit. Also, what is the point of 60 seconds tutorials, I am fine with 3-minute ones. I briefly went to online Lambda school and their lectures are at least 3 hours long each time.
Anyways, the point that he is making in this video and some would struggle is - he calls a function from another "if" function by giving it a parameter. That's a tricky one.Basically, by giving a parameter (name: "Red") , he activates a function above that function. You can see it better if you use Xcode
very bad taste of music