Better Swift Closures Explained - Swift Tips (2023) - iOS

[@iOSAcademy]

Lets connect - linkedin.com/in/afrazsiddiqui

[@eric9964]

Would love to learn more about key paths and other uses, great video!

[@iOSAcademy]

More to come!

[@3eeka]

does the \ is equal to $0 in this syntax?

[@iOSAcademy]

Not exactly. Its similar short hand but the $ is for capture lists for inbound arguments

[@3eeka]

@@iOSAcademy thanks!

[@jansvensson1602]

Great tip, learned something new!

[@iOSAcademy]

Glad to hear it!

[@kamilsuleymanov7197]

Very useful!

[@iOSAcademy]

Glad you think so!

[@gakkieNL]

Great tip! Like the improved readability!

[@iOSAcademy]

Glad it was helpful!

[@ronnie-codes]

Didn't know these functions took keypaths. That's really great, thanks.

[@iOSAcademy]

Happy to help!

[@ViktorMameshyn]

Thanks for your effort, the video is great! The one with computed property is really useful 🙏

[@iOSAcademy]

So nice of you

[@30guarino]

I've been going insane lately and with your video I've finally have ......closure! lol

[@iOSAcademy]

You got this!

[@martinq872]

brilliant!
💡💡💡💡💡💡💡

[@iOSAcademy]

Thanks

[@pawekoaczynski4505]

yeah, I agree - it looks so cool. I kinda wish TypeScript had something similar :p

[@iOSAcademy]

That would be cool!

[@ryankanno2562]

Super cool! Thank you!

[@iOSAcademy]

Thank you too!

[@muncho404]

Thanks Mr. Siddiqui, for discussing this useful topic. Does this mean that KeyPaths by themselves are closures behind the scenes?

[@iOSAcademy]

Thanks & no

[@nikitahalitsky6438]

so the "\." actually replaces $0 or am I getting it wrong? As there should be the cases when we cant omit $0

[@awakeFromNib]

Thanks for the closures. They are still difficult for me.

[@AmitBiswastunebox]

Here is an another closure tutorial: th-cam.com/video/ND44vQ5iJyc/w-d-xo.html

[@iOSAcademy]

You’re welcome 😊

[@awakeFromNib]

@@AmitBiswastunebox Thanks!

[@indomitabletr1834]

What if we use 'reduse', how can we handle this approach. Also, isn't it same behavior like $ sign ?

[@abhilashrajagopal9455]

Nice

[@iOSAcademy]

Thanks

[@OnionKnight541]

this is something that a beginner dev will struggle with for months and years and not know there is a solution to the thing that their intuition tells them they should do.

[@iOSAcademy]

Agreed

[@victorriurean]

👍👍👍

[@iOSAcademy]

Thanks

[@tsalVlog]

\ is backslash.

[@iOSAcademy]

Yep

[@Natena]

Bitchin )) ❤‍🔥🤘

[@iOSAcademy]

Lol thanks

[@Bressam31]

Good to know about this option! But are the following example the same, or are there any hidden benefits of one or other?
- .map(\.isValid)
- .map({$0.isValid })

[@goalsandapps7847]

the latter can also be written as .map { $0.isValid } (except as the very last condition in an "if" or "guard" statement or else a compiler warning will occur).
benefits of anonymous arguments is that you can negate them: .map { !$0.isValid }
also one can have multiple anonymous arguments in the closure: .map { !$0.isValid && $1.isPublic }. AND they look better if combined with loops like .forEach { // do something }
all of which is why i prefer them over key paths.