Swift Closures Explained
HTML-код
- Опубликовано: 2 июл 2024
- Head to squarespace.com/seanallen to save 10% off your first purchase of a website or domain using code SEANALLEN.
I explain what confused me most when learning closures. What do the parenthesis mean? What are the $ in closures (shorthand syntax)? What does @escaping mean? What is Trailing Closure Syntax? This Swift tutorial was created in Xcode 14.
Automatic Reference Counting - Memory Leaks & Retain Cycles:
• Swift - Retain Cycle, ...
iOS Developer Courses
seanallen.teachable.com/
Twitter:
/ seanallen_dev
Hired.com:
hired.com/x/1n01g
Book and learning recommendations that help out the channel if you decide to purchase (Affiliate Links):
Paul Hudson's Hacking With Swift:
gumroad.com/a/762098803
Donny Wals - Combine:
gumroad.com/a/909014131
Mark Moeyken’s SwiftUI Books:
www.bigmountainstudio.com/swiftui-views-book/fzc51
Objc.io Books (Thinking in SwiftUI & Advanced Swift):
gumroad.com/a/656585843
Ray Wenderlich Books:
store.raywenderlich.com/a/208...
#swift #softwaredeveloper #iosdeveloper
Timestamps:
0:00 - These confused me
0:22 - Build a closure and pass it around
3:11 - Closure Types
5:17 - Shorthand syntax - $0, $1
5:30 - Trailing Closure Syntax Intro & Shorthand Syntax
9:34 - SwiftUI - Trailing Closure Syntax
12:09 - @escaping - What does it mean? 
Наука
My iOS Developer Courses - seanallen.teachable.com
I’m going to be honest with you, this was a G-R-E-A-T explanation. I’ve read so many Medium posts and Stack Overflow answers where people either try to sound too smart or they just don’t realize that they’re not speaking in layman’s terms (they’re speaking to other people who don’t need it explained). This took a very simple approach to something complicated and made it simple. FANTASTIC explanation!!! You do a great job of keeping things simple! Seriously. And I like your graphics!
Wow, thanks for the kind words, Lance. I'm happy to hear you appreciated the effort I put into the graphics and simplifying my explanation 😀
That 15 minutes just saved me so much time developing my first native macOS app.
Thank you!!
Best Swift tutorials on RUclips.
Thanks for the kind words, Evan!
(well)->(explained) {Thanks a lot for great video}
I see what you did there...
@@seanallen @Vadiraj Hippargi actually its (explained) -> (well). Your get your explanation and return an answer "well"
WOW! The most Clear and concise explanation I've seen on closures in 6years of developing.
Thank you so much for clearly explaining the $0 and $1 in closures. I have read and studied it so many times but now I just got it in 1 minute.
Thank you!
I wanted to be sure to explain that because the $0 and $1 tripped me up for a LONG time. Glad I could help!
What a wonderful tutorial, clear but also full of knowledge. You really helped me understand the book of swiftUI, thanks a lot !
Simple, nice and clear. Thanks for the video, Sean!
Glad it was helpful!
Before I start this video, I started searching for videos on closures , while actively using “100 days of SwiftUI” lesson plan, but during the first couple lessons involving closures, I could not get out of my head the question “If functions do everything closures do, why then do closures even exist?” So hopefully I get that answer from this video, because this thought it slowing down my ability to progress in learning swift.
My brother! Wow, I am also doing 100 days of Swift with Paul Hudson and I got confused by this as well. 😂 hope you pushed through 💪🏾 I just got here
I absolutely loved the Swift Closures Explained video by Sean Allen. As someone who has struggled to understand closures, this video was a godsend. Sean does an amazing job of breaking down the confusing aspects of closures, like what the parenthesis mean and the shorthand syntax. He explains everything in a clear and concise manner, making it easy for even a beginner like myself to follow along.
I also appreciate the fact that Sean provides a promo code for Squarespace at the beginning of the video. It’s always great to get a discount when you’re starting a new website or domain.
Overall, I highly recommend this video to anyone who is struggling to understand closures, or anyone who wants to brush up on their Swift knowledge. Thank you, Sean, for creating such an informative and helpful video.
Awesome video, Sean! Thank you for all the work you do!
Thanks Tyler. Glad you enjoyed it!
Thanks, that cleared up some things I’ve been putting off for a long time 👍🏻
Thanks again for the generous support, David 😀. I put off REALLY learning closures for a long time too... I was very intimidated by them early in my career.
best teacher i found about swift fundamentals
I've just started delving into the mystery that is closures. Your video helped both for what they are and, especially, why I will need to know them. Thanks!
Glad it was helpful!
Excellent content! This answered so many questions quickly and kindly 👏
Glad it was helpful!
Was confused AF going through swift tour, but this video really cleared everything up.. thanks!!
Glad it helped!
This video came at Great time , currently figuring out this developing game.🙏🏾
Happy to help, Kerrion! Closures were tough for me to figure out when I was just learning.
My thought exactly!
Wow, Sean. You are a very good teacher. Thank you for this. 👍🏼
Glad you enjoyed it, Tom 😀
my issue with this video is it isn’t a discussion of closures in swift but a discussion of a syntactic sugar for function pointers.
unless i missed something, there wasn’t any point where you “closed over” or captured the environment when creating the closure, which is an essential part of closures. i assume you can also do this in swift closures but it wasn’t shown here
Finally my Javascript knowledge helps me out. I picked these up quickly.
Sean you are without a doubt my number 1 iOS teacher. Thank you.
I appreciate the kind words :)
Hi Sean! I've been working on my programing career for about 2 months now. I'm doing the 100 days of swift with Paul Hudson. Even tho this is all still a bit blurry i do appreciate your content since its starting to clear a bit of the fog that i had. Just wanted to stop by and say thanks! You'll probably see me around a bit more ✌
Happy to help. Welcome to the channel!
Hey Sean, thanks for this. Can you make a video about Callbacks? Differences between completion handlers and Callbacks?
8:30 sweet. Gave a special style to the video.
A lot of times when I’m editing the video I’ll think of ways I could have explained things more clearly. That’s what that was :)
Super understandable! Thank you for this video, finally i've got it 🤝
Happy to hear that!
Extremely useful video. I came here for closures and learnt so many things I was confused ab all in one go thanks
Glad it was helpful!
@@seanallen Oh wow I can’t believe you replied. I rly like the way you teach by the way - I just reached ur 3rd video in the visionOS series. Exciting times we live in
Hope you enjoy the visionOS content. Much more to come!
closures are my favourite part of Swift
Not a swift dev but some good information here that if you already know this it makes it connect from a different perspective. Great video
Thanks for the kind words!
Well done, great explanations 👍
Glad you liked it, Stuart!
I should have known that I could trust another Sean to explain this well
Haha, glad you liked it.
Excellent examples! Now do the same example with Async Await
Code magician, expecting more :) with closure and SwiftUI
Hey, very interesting!
Just needed some advice on when should I use a function or computed property with closures?
Explained very well.
Thanks!
I’m on my phone so not sure if this has been said before but it took me a while to figure out how to sort on multiple values….
Tuples!!!!
{ ($0.score, $0.name) > ($1.score, $1.name) }
This will sort first by descending score, then by descending name.
To sort by DESC score and ASC name:
{ ($0.score, $1.name) > ($1.score, $0.name) }
Thanks for the great videos, closures have been a source of mystery for me since I started. One question, in the first example, is the closure being passed in as a type for topStudentFilter?
Another good one.
Thanks Glenn!
very good video!
Glad you liked it!
really nice thanks
No problem, Gregory
Where did the .filter come from? Is it part of the standard library (foundations) along with append, etc.?
Yes. .filter and .sorted are part of the standard library for Swift.
"empty parentheses and Void are the same thing" - man oh man, this is the kind of stuff that takes hours off the head banging waste of time trying to learn
I've been looking for long lists of "this is the exact same result but a different way to get there in Swift" for 3 years
at 2:55 it would be awesome to keep that "other" code visible, comment it out, then we could see and compare the other way.
Thanks for the feedback, Gabe. I'll keep that in mind for future videos. Glad you enjoyed this one!
A Question, is the var topStudentFilter always recalculated when 1. Its called, or 2.when the student array is changed, or3. at both times.
Chuckled at the escaping one 🤣
Just a small glimpse into my inner-monologue while coding.
Looking for ways to identify closures when we see their address in memory graph during debugging.
So often they just show an address. Is it possible to make a trailing closure more recognizable in mem graph? Or to find a closure by address wile debugging? Or to print the address of a trailing closure?
Not that I'm aware of
awesome
Glad you liked it 👍
I am a fan but I think Dr Angela Yu’s course explain it a little better this time.
“@escaping ? …. Who are we running from?” 😂
Thank you for your explanation. Coming from typescript the curly brackets kinda confused me alot. This video really explained well how SwiftUI are just bunch of shorthand ways of writing trailing closures. Could you explain the following code for me? I know what it does, but how did this shorthand version got formed? What would it's "full hand" counterpart be?
```
Button {
showDetail.toggle()
} label: {
Label("Graph", systemImage: "chevron.right.circle")
.labelStyle(.iconOnly)
}
```
I think I figured it out, and that a function can have multiple trailing closures.
Can I see a closure as an interface like in Java
Hi Sean are closures like object in java where you can call them whenever you need them
Not exactly like an object. Closures are functions, but without the function declaration.
Some variables are declared to be Int. Some are Strings. Others are Student, or some other custom struct.
But, variables can also be “ functions that take certain types as parameters and return a certain type”
So you can say:
var aVar: (Student, Int) -> [Student]
Should I invest my time in Swift UI or UIkit? I'm an experienced Android developer and just starting to learning iOS development to boost my portfolio; not necessarily trying to get a job as an iOS dev at least for the next 1 - 2 years
I would recommend you ask this type of questions on Reddit. There's a very active sub for iOS devs. Personally I would start with UIKit since the majority of companies still use it, and it's easier to go from UIKit to SwiftUI than the other way around.
@@hansalucas yeah i can confirm... start with UIKit and then SwiftUI. The other way around will feel like a headache
So now think of escaping as you’re putting popcorn in the microwave. But it’s taking so long to pop, you ask that one friend who’s in the kitchen to wait for it to finish popping and bring it back to the living room?
Lol, that's certainly one way to remember it 😀
I love this!
Suggestion: When teaching to beginners, use unique variable names throughout your code and try not to repeat them between functions that don't end up passing the variable out of it anyways… @6:25 you talk about how we could have used 'persons' instead of 'student' but are using 'student' because it "makes more sense, they're students"… but I see the name 'student' being used at least 13 times on that one screen alone. As stupid as it sounds when I'm learning the new syntaxes I type in variable names like "sparkleUnicorn" and "bubaTheBillyGoat" (silly name placeholders) to keep track of where the variables actually point and go to. When the tutorial overloads with one word being re-used over and over again it just makes my head spin.
I'm sorry about your head. Maybe computer programming isn't for you.
As far as overuse of the word "student" is concerned, it's only seldom repeated assigned as a variable. Mostly student is written with an uppercase S. In these cases, Student is used to refer to the initialiser for instances of the struct Student. To create an array containing instances of Student, the word Student has to be used each time for each instance in order to initialise it to that type, Student, and none other - not UIView, nor UnsafeNonblockingEquitable, nor SparkleUnicorn for that matter. Swift uses an unenforced convention of capitalising the first letter of struct and class names, lowercase for everything else, making the potential for any ambiguity rather less dizzying.
@togidubnus that snide remark was really unnecessary. Your explanation about why `student` appears so often was useful. It’s just a shame the way you started your comment.
slow down plz
Change your video play speed…
The video is great! But his definition of a a closure isn't correct. He says that closures are functions that can be passed around. But all functions can be passed around. The real difference between a closure and a function is that a closure has access to variables in the parent scope without needing to pass them in as arguments. This is a Square-Rectangle relationship. All closures are functions but not all functions are closures. What this video shows is that Swift has a short syntax for defining closures that makes them easy to use functions. But the shorthand syntax isn't what makes it a closure. Non-closure functions don't have access to variables in the parent scope unless you pass them in as arguments. Closures can just access variables in the parent scope without having to pass them in as arguments. The examples in this video are good for creating functions with a shorthand syntax that match the function signature but the examples in this video aren't unique to closures.
In Swift all functions are closures. If you define a function (not with closure syntax) in Swift inside of a scope it will have access to variables in the parent scope. This makes it a closure. But this isn't true in all languages and is an implementation detail of the language.
anyone else absolutely hate some of this syntax?
Most easiest concept in swift is closure
As a flutter developer who is learning SwiftUI I must say that it is the most horrible syntax I have seen for such a simple mechanism known in many other languages such as "Callbacks".
You are speaking much too fast. A learning viewer needs pace to process your information.
Thanks!
Thanks for the generous support! Hopefully this cleared up Closures for ya 👍