Formal typing rules and presentation materials for Swift 6.2's concurrency type system land on GitHub

What landed

A comprehensive repository documenting the Swift 6.2 concurrency type system — with formal typing rules, slides, a paper, and working Swift experiments — has been published on GitHub. It has been reported that the materials were presented at try! Swift Tokyo 2026; video and slide decks are available alongside a LaTeX paper and runnable SwiftPM code. For compiler hackers and language designers, this is the sort of thing you bookmark and dive into immediately. Why? Because it tries to pin down the nitty‑gritty of where code runs and where data lives — questions that matter when you’re wrangling concurrency.

What’s in the repo

The project bundles Marp slides (HTML and PDF), a tectonic-built ACM SIGPLAN paper, and a rich docs section with both Japanese and English beginner guides and the source‑of‑truth typing rules. There’s a Swift package with experimental type‑checking code, a swift‑SIL dump analysis area, and helper scripts for regenerating Mermaid diagrams and TOCs. The repo also includes clear build commands (make targets for slides, paper, diagrams and swift build/test) so you can reproduce the artifacts locally — no guesswork.

Core ideas: Capability and Region

At the heart of the work is a judgment form that tracks capability (@κ — where code runs) and region (ρ — where data lives): Γ; @κ; α ⊢ e : T at ρ ⊣ Γ'. The writeup covers function conversion rules, sending as affine transfer, region merge as context refinement, and closure isolation inference. It ties directly to several Swift Evolution proposals — SE‑0414, SE‑0430, SE‑0431 and SE‑0461 — so this isn’t academic ivory‑tower theory; it’s the language evolution, laid out in formal rules.

Why it matters

Concurrency in Swift is evolving fast, and formal artifacts like these make the changes auditable and implementable. For maintainers and contributors to swiftlang, the repo’s guidelines and typing‑rules workflow are explicitly prescriptive: keep English as the default, avoid fragile section cross‑refs, and treat the Japanese docs as source of truth where indicated. If you care about actors, isolation, and sending semantics — and who doesn’t these days? — this repo is a rare, practical look under Swift’s concurrency hood. Links: the repo (https://github.com/inamiy/swift-concurrency-type-system), slides and video are all in the project.

Sources: github.com/inamiy, Lobsters