3 MISTAKES to avoid when using closures in Swift 😌

[@michaelmayer2613]

I enjoy and learn from almost all your videos that I have watched, but this one was especially useful in clarifying closure behavior. Thanks!

[@swiftandtips]

Awesome explanation Vincent! :D

[@seigen9388]

Very useful advices, I did this way before, but now I understand why exactly this way, thanks

[@iOSTechie]

Thank you so much for explaining so well. Appreciated.

[@wordpressmagics2613]

Great explanation! Thank you.

[@richprice5434]

This was Awsome … what a gem you are Vincent 🎉

[@markaurelius61]

That 20 year old imac with the hemispherical base is a sight. Sign of a real Apple geek.

[@v_pradeilles]

Yeah it looks so good 🤩

[@chesterman18g]

thanks Vincent !

[@KFrench1123]

High quality editing too!

[@v_pradeilles]

Thanks! Also first time my camera was recording in 4K 🎞️

[@pavanmanjani7583]

Superb Thank you

[@evgenykravtsov2157]

Thank you

[@nikolaandrijasevic2271]

What would be the outcome in first tip if we used just “someInteger in “ instead of “[someInteger] in” would it be the same like if we didnt add anything before print statement?

[@justtrust5523]

scheduleTime closures weak self can also be replaced with unowned self

[@victorriurean]

nice