When would you choose a Swift actor over a serial DispatchQueue?
Compare language-level isolation with traditional queue-based synchronization in production iOS code
Tag
Start from this tag, then add more in the filter bar to narrow further. The URL keeps your choices so you can bookmark or share the same view.
Select any combination. A question must include every tag you pick (AND).
Compare language-level isolation with traditional queue-based synchronization in production iOS code
Explain Swift's protocol-driven collection model, then compare Array, Set, Dictionary, and Range by behavior, complexity, hashing, ordering, copy-on-write, and thread-safety tradeoffs
Distinguish race conditions, data races, priority inversion, deadlock, and actor reentrancy anomalies with short Swift examples and practical fixes
Explain that deinit runs where the last strong reference is released, then connect that rule to UI safety, MainActor isolation, and isolated deinit
Group design patterns into creational, structural, and behavioral, then explain real iOS examples from SDKs and your own implementation experience with the tradeoffs that matter in production
Define retain cycles in ARC terms, show the most common ways teams create them, and explain how to prevent and debug them in production code
Explain `MemoryLayout`, padding, alignment, and stride; show why stored-property order changes a struct's footprint; and connect it to arrays, performance, and low-level interop
Start with the race condition, then compare locks, semaphores, queues, barriers, and actors for protecting shared mutable state in real Swift code
Explain when fixed child tasks make `async let` the better tool, and when dynamic fan-out or incremental result handling pushes you to task groups