swift-concurrency
Use when writing or reviewing Swift code that shares state across threads, queues, or isolation domains — locks, lazy properties, mutable statics, caches, or a state store.
- License 许可
- MIT
- 最近更新
- 2026-11-13
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- swift-concurrency
- description
- Use when writing or reviewing Swift code that shares state across threads, queues, or isolation domains — locks, lazy properties, mutable statics, caches, or a state store.
03 SKILL.md 正文
Swift concurrency pitfalls
REQUIRED BACKGROUND: vvkit:writing-tests for when a test is required. Test shapes for these
hazards: vvkit-swift:swift-testing → references/concurrency.md.
Mistakes that shipped. Each is invisible from the file in front of you, and each has a measured cost.
lazy var is not atomic
- Swift's
lazyhas no synchronisation. Threads racing first access each run the initialiser and can get different instances. - Measured: 200 owners under contention produced 209 initialisations and 201 distinct objects — shipped as a second timer and a reference count that never converged.
- Plain
lazyonly where every first-access path is provably single-threaded; elsewhere an atomic one-shot initialiser. - The window closes after first access, which makes the obvious test useless — the first-access
trap in
vvkit-swift:swift-testing.
A mutable static var is shared by every thread
-
A bare
next += 1reached from several initialisers handed out duplicate ids. Lock it, or make it immutable. -
Check-then-act is the same race:
if let existing = Self.cached { return existing } Self.cached = make() // two threads both get here, and both construct return Self.cached!
Per-field locking does not compose
- Fields describing one thing go in one struct behind one lock or store — never a lock each. Per-field atomics served one rotation item to two consumers, and paired a nil user id with the previous user's session id.
- A store makes each transition atomic, not a caller's sequence. Two getters are two reads. Callers needing several fields coherently get one accessor that reads state once.
- A transition never calls out — a database read, a delegate, a subscription, or releasing the last reference to something whose teardown re-enters the store self-deadlocks a non-recursive lock. Resolve outside, write the result in. Two threads both resolving is usually the cheaper correct trade — comment it, so nobody pulls the call back inside.
Read-modify-write is not one operation
value = value + 1 on a shared subject, relay or property has a gap. Use a lock-protected box or an
atomic for counters.
What counts as concurrency
- A lock, or a serial/barrier queue guarding state
Thread,DispatchGroup,DispatchSemaphoreactor,nonisolated(unsafe),@unchecked Sendable,Task.detached- A reactive chain observing or subscribing on a non-main scheduler
- State mutated from a timer, KVO, a notification, or a network or delegate callback not pinned to main
Not by itself: a chain created, observed and disposed on main. The trigger is cross-domain reachability.
@unchecked Sendable is a claim to justify
It silences the compiler; it makes nothing safe. Every use carries a comment naming the invariant — which lock, which queue, which single-writer discipline. Cannot name it: the conformance is wrong.
04 同仓库更多 Skills
no-heading
Use when proving that the validator rejects a body with no H1 and a force-loading @-link.
wrong-name-does-not-match-dir
Dispatches a subagent per task and reviews between each one.
writing-tests
Use when adding or changing behavior, fixing a bug, or judging whether an existing or generated test earns its place.
writing-skills
Use when authoring or editing a skill, agent, command or hook for this kit, or when deciding whether a piece of guidance belongs in a skill at all.
writing-project-instructions
Use when creating or editing a CLAUDE.md or AGENTS.md, when it has grown long, or when a rule in it also exists in an installed skill.
writing-logs
Use when adding or reviewing log statements, or when deciding what level a message belongs at.