In WWDC25 sessions, we see @concurrent but which swift-evolution proposal did it appear?
Asked on 2025-06-13
1 search
The @concurrent attribute mentioned in the WWDC25 sessions is part of the concurrency improvements in Swift 6.2. However, the specific Swift Evolution proposal where @concurrent was introduced is not detailed in the provided context. If you are interested in the evolution of Swift concurrency features, you might want to check the Swift forums or the Swift Evolution repository for detailed proposals and discussions.
For more information on concurrency in Swift, you can refer to the session Embracing Swift concurrency (10:22) from WWDC25, which discusses introducing concurrency and related features.
Embracing Swift concurrency
Join us to learn the core Swift concurrency concepts. Concurrency helps you improve app responsiveness and performance, and Swift is designed to make asynchronous and concurrent code easier to write correctly. We’ll cover the steps you need to take an app through from single-threaded to concurrent. We’ll also help you determine how and when to make the best use of Swift concurrency features – whether it’s making your code more asynchronous, moving it to the background, or sharing data across concurrent tasks.
Explore concurrency in SwiftUI
Discover how SwiftUI leverages Swift concurrency to build safe and responsive apps. Explore how SwiftUI uses the main actor by default and offloads work to other actors. Learn how to interpret concurrency annotations and manage async tasks with SwiftUI’s event loop for smooth animations and UI updates. You’ll leave knowing how to avoid data races and write code fearlessly.
What’s new in Swift
Join us for an update on Swift. We’ll talk about workflow improvements that make you more productive, and new and modernized library APIs for fundamental programming tasks. We’ll show examples of Swift adoption throughout more layers of the software stack. Finally, we’ll explore new language features for both improving approachability of concurrency, and achieving peak performance when you need it.