I was thinking the exact same thing. This talk is still extremely useful though even with all the changes like actually calling it asociatedtype and the addition of ´some´ and ´any´ etc.
Nice talk. I use PATs to define UseCases from Robert C. Martins Clean Architecture. They have become the main building block in my code for defining modules.
TLDR; "Am I going to need to turn all my code generic just to deal with things that support equality? Yes. @30:45 It helps to think about them as "a new thing, not a broken version of an old thing". Thanks for the video.
Ugh...if the syntax allowed “func eat(f:Food:Grass){}” or “func eat(f:Food.Grass){}” then the compiler would have all the information it needs to meet the covariance requirement.
I’d be more forgiving if swift was not backed by a trillion dollar company that could easily solve this problem by adding existentials with a snap of a finger. Same goes with not having better concurrency and Xcode tooling.
