Yesterday you learned the basics of closures, but today things get a little trickier. But that’s OK: Benjamin Franklin once said, “energy and persistence conquer all things” – you can do this!
Sometimes closure syntax can be a bit hard on your eyes. If you find it a bit overwhelming – if you’re staring at some code and aren’t 100% sure of what it means – just go back one video and watch it again.
Today you have seven one-minute videos to watch, and you’ll learn about how closures accept parameters and return values. Once you’ve completed each video you can go over any optional reading if you need it, then take a short test to help make sure you’ve understood what was taught.
To make things a little less intimidating, I’ve split up today’s topics into two sections: the least you need to know to continue, and more advanced topics that will really develop your learning. Keep in mind that I’ve already said closures are hard, so I hope you can appreciate that more advanced closures are doubly hard – don’t feel bad if you try the more advanced topics and think you’ve had enough and want to move on!
If you make it through those, you’re most of the way to understanding how closures are used in Swift and why they are important. However, if you want to see more advanced usages of closures you’re welcome to press on!
Remember, stay accountable: tell the world that you’ve just learned all about closures in Swift, and discuss them with others who are learning too.
Need help? Tweet me @twostraws!
SPONSORED Catch bugs as soon as they happen and know exactly why a crash occurred. Instabug's SDK grabs all the logs they need to fix bugs, crashes and performance issues in minutes instead of days. Get screenshots, device details, network logs, repro steps, and tons of other critical insights needed to resolve issues and prioritize product backlogs straight from your dashboard. It only takes a minute to integrate!
Link copied to your pasteboard.