What I like most about these tutorials you make is you keep the font large something a lot of tutorial makers refused to understand

I still can't understand how the captainFirstSorted function is working. what is the logic of that function?

For everyone that does not understand don´t worry, it is just that you need a bit of computer science basic knowledge. (I highly recommend to take an entry level University Grade CS course like harvards CS50, which is free) the sorted() function in swift basically goes through the array always just comparing two names with each other, putting the one which is alphatecial first in front until the whole array is sorted. The function does that by checking if name1 is less than name2 (in terms of alphabetical order) if that comparison returns back a true means nothing has to be done, as the first name is already in front and alphabetical lower. If the comparison returns a false the function will switch the position of the two names. The closure here just tells the sorted() function to do exactly that EXCEPT if one of the two names that gets compared is Suzanne. So if Suzanne is standing in front of the other name (which means name 1 == Suzanne) return true so it stays in front, if Suzanne is not in first order, then return false and switch Suzanne in front. If Suzanne is not in the comparison, just do the regular name1 < name2 check. I feel like Paul should have mentioned that, for absolute beginner programmers without any CS background. Hope that helps!

I was confused how name1 < name2 in the function logic accounted for all the names in the array, but it doesn’t! The logic behind the scenes of the sort() function tells the computer to go through the entire array of names. 13:10 Update: this explanation from ChatGPT helped a lot. **Concept of Pairwise Comparison**: Sorting algorithms, especially comparison-based ones, work by repeatedly comparing pairs of elements to determine their relative order. The exact pairs that get compared, and the sequence in which these comparisons occur, vary depending on the specific algorithm. When you provide a function that contains a > b as part of the functions logic flow to the `sort(by:)` method, it essentially acts as a "rule" or "guide" for the sorting algorithm. Every time the algorithm needs to determine the relative order of two elements, it will call this function with those two elements

one of the only good videos on closures I've found ... thank you

A lot of this makes sense. One thing I'm struggling with, is a practical reason as to why one might want to *copy* a function at all? Why not use the original function?

When they say KZfaq is a good place, they're probably referring to this Channel. Thanks Paul for such an enlightening explanation.

That was such a lovely explaination. Thanks mate!

I just paused the video to comment on your brilliant teaching style and simple and clear explanation. Thank you so much! coming from JS, Swift seems like an exciting and beautiful language.

Oh my God!!! Thank for such a brilliant explanation!!!

This made things clear. many thanks!

Thank you for the reassurance I'm not a dumbass - I actually needed that.

Omg, I finally understand closures! Thank you Paul!

Nice and deep explanations. Thank You.

Im killing myself trying to understand how name1 and name2 sort Suzanne to be first ... Can anyone help to explain to me ?

I’ve had to watch this video about 5 times now. I think I’m starting to understand Closures 😅

thank you for video

Coming from Python, Java and js. I have learned to both love and still misunderstand swift’s idiosyncrasies

Great video, very well explained in my opinion. I think the benefit of closures in my mind is being able to differentiate between functions which are general purpose and have utility in many places versus a very specific sort algorithm used to collect/filter just the data you want. Potentially it would have been a useful tool to sell the utility by going on to "need" a captainLastTeam object directly after this.. Would you go and define a whole new function for this sorting algorithm.. or would you tightly couple the algorithm in a compact way exactly where its required using closures. Maybe you have 10 slightly different filters you need to apply to your object one after the other... What then?

Thank you! You explain the concepts very well

Thank u

I watched this and the following video 3 times and each time was left with the impression that this sorting function could only manipulate the order of the first 2 items in the array. In my opinion this lesson would benefit from a reshoot. Don’t mean to sound unappreciative, I love the content and teaching method usually, I just think this video skims certain things and really got me hung up.

Great & very useful! Thanks!

11:10 So we are passing 2 parameters to the function: name1 and name2, but how does it work correctly if we are passing a String array instead of strings?

pure gold secrets at free of cost for ios devs.

You really gotta explain why something works a certain way or else you might as well not bring it up. You skip right past what sorted(by:) actually does with the boolean value, which leaves a lot of people more confused than before, as seen in these comments.

So it works like a java method. I don't get the significance. Are you saying the return type of a swift func is not the data type? If it returns a string it is not a string?

I love you

As a beginner I was confused with name1 and name2 representing all the positions in the array until I switched name1 to return false and name2 to return true. Then everything clicked in my head.

You are so good with ur dogs :) keep on running!

Hey, Paul, is this a correct version of a closure? let whyUseClosures = { print("Because you can use fewer lines of code in many places!!!!") } whyUseClosures()

Somewhat understood the workabout but got lost into thier functionality. Having to assume they come in handy with variable or constant asignation

For anyone still trying to figure the section with "let captainFirstTeam" in terms of the boolean outputs, I understood best when taking another commenter's suggestion. Blushing Gun stated: "As a beginner..." (hopefully he doesn't delete this comment lol) If you swap the return true to false in the first 'if name1' statement, and do the same for 'if name2' by swapping it to true, you'll see the output shifts the desired name, "Suzanne" to one other side of the spectrum. If you play around with the code further, you could try swapping the final return line "name1 < name2" and seeing what it does. Sometimes I find this the best way to help me understand the syntax when I find myself confused. Hope this helps someone!

I still do not get it. Why not just call the function with parameter? To me, closures simple mean to give the fubction another name. So what? I see no advantage.

Not sure if this helps anyone. Looking at the teams array ["Gloria", "Suzanne", "Piper", "Tiffany", "Tasha"] this is how the logic works: Since the captainFirstSorted takes two variables, the second value in the array is compared to the first so I have put some print statements and this is how it looks like Suzanne less than Gloria true - (which means Suzanne is 1,Gloria is 2) Piper less than Gloria false - (which means Suzanne is 1,Gloria is 2, Piper is 3) Tiffany less than Piper false - (which means Suzanne is 1,Gloria is 2, Piper is 3, Tiffany is 4) Tasha less than Tiffany true - (which means Suzanne is 1,Gloria is 2, Piper is 3, Tasha is 4, Tiffany is pushed to 5) Tasha less than Piper false - (which means Suzanne is 1,Gloria is 2, Piper is 3, Tasha stays the same at 4, Tiffany is pushed to 5) So based on this, the sorted array is ["Suzanne", "Gloria", "Piper", "Tasha", "Tiffany"] To explain a bit further, lets change the order of items in the array to ["Tasha", "Piper", "Tiffany", "Suzanne","Gloria"] Piper less than Tasha true - so Piper is 1, Tasha is 2 Tiffany less than Tasha false - so Piper is 1, Tasha is 2, Tiffany is 3 Suzanne less than Tiffany true - so Piper is 1, Tasha is 2, Suzanne is 3, Tiffany gets pushed to 4 Suzanne less than Tasha true - Piper is 1, Suzanne moved to 2, Tasha pushed to 3, Tiffany at 4 Suzanne less than Piper true - Suzanne moved further to 1, Piper pushed to 2, Tasha still at and Tiffany at 4 Gloria less than Tiffany true - Suzanne 1, Piper 2, Tasha 3, Gloria comes at 4 and Tiffany pushed to 5 Gloria less than Tasha true, Suzanne 1, Gloria moved to 2, Piper pushed to 3, Tasha moved to 4, Tiffany at 5 Gloria less than Piper true - Suzanne 1, Gloria still stays at 2, Piper at 3, Tasha at 4 an Tiffany at 5 Gloria less than Suzanne false - Suzanne stays at 1, and then comes Gloria, Piper, Tasha and Tiffany Result is [“Suzanne", "Gloria", "Piper", "Tasha", "Tiffany"] Must be a silly explanation to some but this is how I understood how this works

I disagree when you say void is nothing. I get what you are trying to say. But I believe that makes more confusion latter on for a new swift programmer. Void is an alias for an empty tuple. Tuples are also types in swift. So, definitely empty tuple it is something.

Swift Closures are easy if you think in Javascript. In Javascript 'speak' a Swift Closure is simply a callback function, which can be a regular function declaration or an anonymous arrow function, and which is passed as a parameter to an higher-order function. The main difference is the function type [ ( param: paramType ) -> ReturnType in ] that must be included at the start of the function code block: { function type + function code block } Although this has been well explained here.

Paul Hudson is the Pope of the Holy Church of Swift and good Lordy he’s a’ Preachin!

Fking love you mate!!! God bles you

The sorted function could have been explained better.

Fank You

I'm sorry horrible example because we don't know the implementaion of sorted. How about creating a custom sorted and explain how the "anonymous" function performs.

somebody give me 2x paracetomol tablets please....

my god, how can i be so dumb? this does not enter my head at all

Is it needed no. why do it ? because the apple God told me so.

interesting fact: Swift was actually named after famous singer Taylor Swift

i have to end it here. this isn't for me. way too complex to listen to and process and we're not even at day 10. watching and rewatching a 20 minute video just to not get it in the end when i need to make something with this thing seems like a waste of time. the last exercise with all the error catching was too much too soon and i know it's only going to get worse from here on. i don't understand where do you guys find the motivation to keep going. if you go back to the start, this whole 100 day course is just enough to land you a entry level job. absolutely ridiculous.