You probably remember learning about closures a couple of weeks ago, mostly because it was a particularly tough part of the course. Since then I’ve tried to work them back in slowly so you can master them little by little, and today it’s time to dive into them with our own closure.
I think you already know what I’m going to say, but I’ll say it anyway: this isn’t going to be easy. But the US general George Patton once said, “accept the challenges so that you can feel the exhilaration of victory” – when you finally feel like you understand closures (which might be today!) that’s when you know you’re really getting comfortable with Swift.
Today I’ll be introducing a new aspect of closures called capture lists. To make things easier, I prepared a new article just for this series that explains in detail what capture lists are and how they work – you should start by reading that.
Today you should work through the article on capture lists, then the three topics from project 5.
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.