Edit Ever since I’ve upgraded to Xcode 16.1 I’ve experienced significant issues with finding callers. Yet aside from Xcode being broken, this post is still applicable for having a correct understanding of when / why / how Xcode should and shouldn’t work. Sample Project Download the sample project if you want. You don’t have to though. The project doesn’t even need to be ran. It’s just provided for context. I’m going to discuss two gotchas I hade with Xcode....

I always thought that if you just use {get} on a protocol variable, then you can still set it i.e. it doesn’t matter if you give it a setter or not. That’s not true. It really depends on which compiler checks come in to place. Compiler checks are different depending on the type you want a variable to be. Can you guess which of the two snippets will compile? Snippet A...

Progressive disclosure - 00:00:37 You don’t need to onboarding everything all at once onto Swift Concurrency. You can only onboard a single function, class or module at a time. Actors - 00:04:12 Similar to class, struct and others, actors are a type. They’re named actor because: XXXX . Actors give you synchronized and thread safe access to all properties and functions. 00:08:20 - This comes at a cost. Any access to any member function of the actor from outside will have to be marked with await...