@dave the context was one of the team talking about how our legacy is not the code we write but the emoji we leave behind, to which i responded with the howdy-jelly emoji, to which the PO responded by donning his hat and glasses
Swift Concurrency question: I have a network client (class) that is wrapped by an actor (ModelActor for SwiftData) at a higher level, however using the network client as a property of the actor results in Sendable warnings whenever I try to call any of it's methods.
@tonyarnold it either needs to be an actor or Sendable. the trick is, if you make it an actor, you can only access its methods and properties from an async context. if it's Sendable, it either needs to be non-mutable, or you need to lock mutations and likely mark it @unchecked