"any" Keyword and Existential types in Swift

[@AlexPeresedov]

It is so rare when a tutorial is made with so readable examples so I can watch it even on my phone. Thank you!

[@swiftandtips]

Thank you very much ☺️

[@tundsdev]

Great video, love the animations and clear explanation

[@swiftandtips]

Thank you very much 😄

[@ЭдуардЕленский-н8ч]

In WWDC22 on this topic the ppl were saying easy rule: better use some first and if compiler doesn’t like it change to any. I guess in ur examples if Animal doesn’t have Self or associated requirements then u can move to some (so its kinda lightweights the function signature in this case in comparison with generic variant)

[@indomitabletr1834]

You really know what is going on at memory, i am appreciated

[@Cerezo074]

Thanks for your explanation, pretty clear sir!!!!

Great way to explain any keyword Pitt! Great video

[@swiftandtips]

Thank you very much Jesus! 😊

[@FredWhosDead]

Great video Pete!

[@swiftandtips]

Thank you very much Ed! :D

[@filipvabrousek6900]

Well explained! Many thanks!

[@cil7ea]

love the explanation!

[@swiftandtips]

Thank you very much! 😊

[@theflyingsolo]

I'm glad I found your channel from LinkedIn! Great content, these higher level concepts are so good to know but might get missed by the algorithm. Everyone boost!

[@swiftandtips]

Thank you very much!!

[@blaze9590]

i think it's witness table in this case and not vTable

[@swiftandtips]

What’s that Blaze? 😲

[@blaze9590]

@@swiftandtips witness table is basically what’s used in dynamic lookup of methods/properties for existential types(protocols). Apple engineers talked about it in wwdc 2016 on performance. Vtable on the other hand is what’s used for classes that support inheritance/polymorphism/dynamic dispatch.

[@swiftandtips]

I didn’t remember talk. Thanks for the explanation!

[@salmansiddiqui9522]

Why are we using any if we dont have any performance ? or just to tell compiler that its existential type.

[@swiftandtips]

Hi Salman, that’s a good question!. This is to make a clear distinction between generic constraints and existential types. I recommend you to check the proposal discussion. I left a link in the description 👍

[@markvllar]

So adding the any keyword will not resolve the performance implications that you’ve talked about?

[@swiftandtips]

Hi Mark, No, it just explicitly mark the usage of an existential type, that’s it. 👍

[@swiftandtips]

Hi @Hitesh Agarwal, short answer is yes, but also this is to clearly distinguish between opaque types vs existential types.

[@andrejkling3886]

Thank you... Can you show more real examples?

[@swiftandtips]

Hi Andrej, just use it every time you declare a protocol type in your code, cheers!

[@KFrench1123]

Well done! Thank you :)

[@byaruhaf]

is there a way to trigger the warning in swift 5.6?

[@swiftandtips]

Hi Franklin, that's a good question! I tried using frontend flags in Xcode (enable-explicit-existential-types) but it doesn't work. I will investigate and let you know if I got something. Cheers!

[@ЭдуардЕленский-н8ч]

The easy way I can tell right now is Swiftlint rule

[@byaruhaf]

@@ЭдуардЕленский-н8ч Thanks which rule is it?