What is @Sendable in Swift?

@Sendable marks closures/functions safe for concurrency: captures must be Sendable types, by value via lists—no mutable refs across isolation domains.

How do I fix 'Reference to captured var in concurrently-executing code'?

Add capture list [x] for snapshot copy, ensure x is Sendable. Or refactor to immutable let.

Do all closures need @Sendable?

Only those crossing domains: actor args, Task captures, async handoffs. Single-threaded

💻 Programming Languages

Swift's @Sendable: The Passport Closures Need for Concurrency Chaos

Swift promised concurrency nirvana with actors and async/await. But closures? They were smuggling unsafe state across domains. @Sendable slams the door on bugs.

theAIcatchup Apr 10, 2026 4 min read

Swift closure with @Sendable crossing actor isolation boundaries

⚡ Key Takeaways

@Sendable ensures closures capture only safe, copyable values—no mutable heap boxes across concurrency domains. 𝕏
Use capture lists like [x] for vars to create immutable snapshots, dodging compiler errors. 𝕏
Powers real actor patterns: filters, maps, transforms in background Tasks without races. 𝕏

Published by

theAIcatchup

Community-driven. Code-first.

#@Sendable #Swift #Swift actors #Swift concurrency #actor isolation #actors #closures #closures capture #concurrency #data races

Worth sharing?

Get the best Open Source stories of the week in your inbox — no noise, no spam.

Originally reported by Dev.to

⚡ Key Takeaways

The 60-Second TL;DR

theAIcatchup

Share this article

Worth sharing?

Related Stories

JavaScript's Hidden Execution Contexts: Why Your Code Ghosts You

The Sneaky Data Race That Slips Past 'Correct' Atomics in Lock-Free Code

Timsort: The Hybrid Beast Sorting Billions of Lists Daily

Rust's Match: The Bulletproof Pattern Matcher That Crushes Switch Statements

Stay in the loop