Opaque Type vs Protocol in Swift | Associated Type | Generics | iOS

[@arunbenjamin8278]

Your topics Selection is good where developers get lot of confusions.

[@bapathimallikadevi9601]

crystal clear explanation . Really appreciate the way you are teaching others

[@maheshparmar5647]

You really cleared all the doubts related to the topics..🙌

[@iCode_Happy_Coding]

Glad to hear that

[@piyushgeorge1847]

Your channel covers very useful topics. keep up the good work 👍👍👍

[@iCode_Happy_Coding]

Thanks Piyush 🙂

[@anaghabhagwat7771]

Very well explained.👍Thanks for sharing your knowledge !!

[@keshurai2700]

Your selection of topics is so good.

[@iCode_Happy_Coding]

Thanks Keshu 🙂

[@jeevank8550]

All of your videos are very informative. Especially for Senior or Mid-Senior level iOS devs like me.

[@iCode_Happy_Coding]

Glad that you liked the videos 🙂

[@ShubhamGupta-qo2pt]

Worth watching on Monday with breakfast :), keep up the good work.

[@iCode_Happy_Coding]

Thanks Shubham 🙂

[@nitishnayak8664]

well done Pallav . crystal clear explanation . Really appreciate the way you are teaching others.

[@vinayakpaul2251]

I have learnt a lot from your channel even possess lot of experience in Swift. Keep up the good work

[@shanmugamsekar4044]

very well explained.👍

[@shantibhatt4867]

Thank you, It's very helpful Please do videos on SOLID principles and xcode instruments usage

[@iCode_Happy_Coding]

Thanks for the suggestion Shanti. I'll try covering it 🙂

[@vickywang5049]

My takeaways: Generics is the placeholder of types used in functions signatures (like a template). It allows the caller to decide the actual type whereas the function doesn't care about it at implementation. Syntax: func function -> [T] {} Opaque type is a placeholder in function returns. It hides the concrete type from the caller, but the function's implementation and compiler knows exactly what it is. Syntax: with keyword "func function() -> some Protocol{}" Associated type is the type placeholder inside of protocols. It makes protocols more generic. Anyone who adopts from protocols with associatedtype must specify the actual type first. Syntax: associatedtype typename Protocol is the "blueprint" of a set of properties and functions that must be implemented if a structure, class, protocol wants to conform to it. Syntax: protocol protocolName {}

[@vickywang5049]

An example that can be solved by opaque type: If you have a generic protocol with associatedtype, and you don't want to reveal the concrete type of the function returns to the caller, you can use "some" keyword to return an opaque type instead.

[@pr1tham]

Very good content, Please keep this up. Thanks.

[@seunolalekan8987]

Thanks a bunch man! This was an excellent explanation.

[@pawanmanjani1298]

Superb Keep posting🙂

[@LittleLearners-junior]

superb videos please keep uploading.

[@dhavalumraliya2307]

Just perfect 🔥🔥🔥🔥🔥 it would be very great if you make a video on web socket.

[@iCode_Happy_Coding]

Thanks for the suggestion Dhaval. I'll try covering it 🙂

[@King_Slayer_06]

Thanks for the great explaination Pallav! At 11:57 i was getting suggestion to change the return type to "any Card" instead of "some Card" (Im using Xcode 15.0.1). What is the difference between "any" and "some"?

[@VinothKumar-zl2ht]

Super videos, please upload in 1080p.. its good in UHD monitor.

[@iCode_Happy_Coding]

Thanks for the feedback Vinoth, I’ll look for it 🙂

[@ankitbhana9852]

Just amazing🙌🏻

[@iCode_Happy_Coding]

Thanks 🙂

[@dhivyavenkatachalam7724]

Indeed useful video!!

[@MrAbhijithadkar]

You should consider uploading 2-3 videos @pallav. Nice topic covered very easily. Thanks and keep it up.

[@iCode_Happy_Coding]

Sure Abhijit, I'll try covering theses topics in detail. 👍🏼

[@puneetpal1466]

It was awesome... Thank you so much :) 😊

[@iCode_Happy_Coding]

You're so welcome! 🙂

[@ananthakrishna9672]

Great information. I have small doubt how to decide struct vs class

[@iCode_Happy_Coding]

Thanks for the suggestion Anantha 🙂. I’ll try to cover class vs struct in detail (including usage).

[@ananthakrishna9672]

@@iCode_Happy_Coding thank you.

[@akshaygawade272]

is it build error because associated Type is protocol or it can be give build error even if associated type is string.

[@krishnachowdary8447]

Love you man

[@otniel2663]

thanks for sharing

[@abymathew575]

nice explanation bro.

[@iCode_Happy_Coding]

Thanks 🙂

[@ANILKUMAR-vv1fz]

it was awesome

[@reshmaunni7017]

Thank you so much sir

[@deveshtyagi]

Amazing

[@iCode_Happy_Coding]

Thanks 🙂

[@deveshtyagi]

🔥

[@maqusss]

I saw much better example on hackingwithswift. Consider functions makeInt and makeString that both return "some Equatable". Compiler will allow comparison "makeInt() == makeInt()" or "makeString() == makeString()" but won't allow "makeInt() == makeString()".

[@iamarorarishabh]

👍👍

[@victorriurean]

[@keshavkumar1522]

Thank you so much for your effort in delivering such kind of valuable content on youtube. All your videos are so informative with a practical example. Wishing you and our channel great success. Keep doing a lot. Kindly do videos on MVVM-C, MVP, VIPER Patterns. Most of the developers struggle with animation stuff. So, please do a tutorial series on CoreAnimation, BezziarPath, Custom Layouts, etc. Thanks again.

[@iCode_Happy_Coding]

Thanks for the kind words Keshav. Did a video on Bezier Curves after your suggestion 🙂