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

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

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

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

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

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

Thanks a bunch man! This was an excellent explanation.

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

Your selection of topics is so good.

Your content is awesome! Please also cover Opaque Type & Type Erasure.

Very good content, Please keep this up. Thanks.

very well explained.👍

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

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

Indeed useful video!!

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

superb videos please keep uploading.

Just amazing🙌🏻

Love you man

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

thanks for sharing

Superb Keep posting🙂

Thank you so much sir

it was awesome

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

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"?

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 {}

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

nice explanation bro.

Amazing

🔥

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.

I’m even more confused. Is a generic and associated type the same lol. It seems that way. Just used it two different areas.

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

👍👍

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()".