Advertisement · 728 × 90
#
Hashtag
#swiftconcurrency
Advertisement · 728 × 90
Preview
GCD, OperationQueue, Swift Concurrency. iOS concurrency interviews span 15 years of APIs — from raw threads to GCD queues, OperationQueue dependencies, and Swift’s structured…

I just published GCD, OperationQueue, Swift Concurrency. medium.com/p/gcd-operat...
#iOS #Swift #GCD #iOSDev #SwiftConcurrency #DispatchQueue #OperationQueue #iOSInterview #Actor #AsyncAwait #MainActor #Sendable #TechInterview #MobileDevelopment #SoftwareEngineering

2 1 0 0
Preview
RxSwift or Combine? The Question That Exposes Whether You Actually Understand Reactive Programming Senior iOS interviews don’t just ask you to name operators. They ask you to explain backpressure, retention cycles, scheduler switching…

I just published RxSwift or Combine?
The Question That Exposes Whether You Actually Understand Reactive Programming medium.com/p/rxswift-or...
#iOS #Swift #RxSwift #Combine #ReactiveProgramming #iOSInterview #SwiftUI #SwiftConcurrency #MobileDevelopment #TechInterview #iOSDev #AsyncAwait

1 0 0 0
Preview
Stop Winging It: iOS State Management Strategies Interviewers Actually Ask About Real Q&A, working Swift code, and the mental models that separate senior engineers from the rest — all in one deep dive.

I just published Stop Winging It: iOS State Management Strategies Interviewers Actually Ask About medium.com/p/stop-wingi...
#iOSDevelopment #Swift #StateManagement #SwiftUI #MVVM #TCA #iOSInterview #MobileEngineering #Combine #SwiftConcurrency #SoftwareArchitecture #iOSArchitecture

0 0 0 0
Preview
They Asked Me “How Do You Abstract Your Data Layer?” The Repository Pattern in Swift: clean architecture, real code, and the interview answers that separate mid-level developers from seniors

I just published They Asked Me ‘How Do You Abstract Your Data Layer?’ medium.com/p/they-asked...
#iOSDevelopment #Swift #CleanArchitecture #RepositoryPattern #iOSInterview #MVVM #SwiftUI #Combine #SwiftConcurrency #MobileDevelopment #SoftwareArchitecture #TechInterview #iOSDev #CoreData #URLSession

2 0 0 0
Core Data Reform - Achieving Elegant Concurrency Operations like SwiftData Explore how to bring SwiftData's elegant concurrency to Core Data. Learn to implement a Core Data version of @ModelActor using custom executors for safer, efficient data handling.

This preserves Actor's isolation safety while seamlessly bridging legacy APIs.

See how I use this technique to achieve SwiftData-like elegant concurrency in Core Data 👇

fatbobman.com/en/posts/co...

#Swift #SwiftConcurrency #Actor

1 0 0 0
Preview
Swift Concurrency—Part 1: Tasks, Executors, and Priority Escalation Swift 6 introduced a new approach to concurrency in apps. In this article, we will explore the problems it aims to solve, explain how it works under the hood, compare the new model with the previous one,...

Swift Concurrency—Part 1: Tasks, Executors, and Priority Escalation #Technology #SoftwareEngineering #ProgrammingLanguages #SwiftConcurrency #Programming #SoftwareDevelopment

1 0 0 0
Preview
Understanding Data Races: A Visual Guide for Swift Developers Thoughts about Software and Building Software

What do robot toddlers and coloring pages teach us about data races? First in a series building concrete mental models for Swift Concurrency. Feedback welcome!

krishna.github.io/posts/unders...

#swift #concurrency #swiftconcurrency #swift6

5 0 0 0
Preview
MainActorMessage & AsyncMessage: Concurrency-safe notifications Dive into notifications and Swift concurrency. Discover the updated notification API that ensures thread safety.

📬 𝑴𝒂𝒊𝒏𝑨𝒄𝒕𝒐𝒓𝑴𝒆𝒔𝒔𝒂𝒈𝒆 & 𝑨𝒔𝒚𝒏𝒄𝑴𝒆𝒔𝒔𝒂𝒈𝒆: 𝑪𝒐𝒏𝒄𝒖𝒓𝒓𝒆𝒏𝒄𝒚-𝒔𝒂𝒇𝒆 𝒏𝒐𝒕𝒊𝒇𝒊𝒄𝒂𝒕𝒊𝒐𝒏𝒔 by Antoine van der Lee (@avanderlee.com)

Notifications crashing with concurrency errors? Replace unsafe 𝑛𝑜𝑡𝑖𝑓𝑦() with thread-safe alternatives that work seamlessly with modern async/await patterns.

#SwiftConcurrency #Notifications

2 0 0 0
Concurrency Step-by-Step: Conforming to Protocols If there’s one topic that I find intimidating, it’s protocols. They are very powerful and in extremely wide use. But I’m sitting here, trying to figure out how to lead into this discussion and I’m…

⚡ 𝐶𝑜𝑛𝑐𝑢𝑟𝑟𝑒𝑛𝑐𝑦 𝑆𝑡𝑒𝑝-𝑏𝑦-𝑆𝑡𝑒𝑝: 𝐶𝑜𝑛𝑓𝑜𝑟𝑚𝑖𝑛𝑔 𝑡𝑜 𝑃𝑟𝑜𝑡𝑜𝑐𝑜𝑙𝑠 by Matt Massicotte (@massicotte.org)

Struggling with protocol conformance across actor isolation boundaries? This breakdown explains isolated conformances and protocol isolation mismatches in Swift 6.2.

#SwiftConcurrency #Swift

2 0 0 0
Preview
Using MainActor.assumeIsolated to Solve Legacy API Compatibility Issues with Swift 6 Use MainActor.assumeIsolated in a synchronous context to create closure safely on the main thread and return Sendable types, achieving full compatibility without warnings or errors.

🔄 𝑈𝑠𝑖𝑛𝑔 𝑀𝑎𝑖𝑛𝐴𝑐𝑡𝑜𝑟.𝑎𝑠𝑠𝑢𝑚𝑒𝐼𝑠𝑜𝑙𝑎𝑡𝑒𝑑 𝑡𝑜 𝑆𝑜𝑙𝑣𝑒 𝐿𝑒𝑔𝑎𝑐𝑦 𝐴𝑃𝐼 𝐶𝑜𝑚𝑝𝑎𝑡𝑖𝑏𝑖𝑙𝑖𝑡𝑦 𝐼𝑠𝑠𝑢𝑒𝑠 𝑤𝑖𝑡ℎ 𝑆𝑤𝑖𝑓𝑡 6 by @fatbobman.com

Bridge legacy Apple APIs with Swift 6's strict concurrency using 𝑀𝑎𝑖𝑛𝐴𝑐𝑡𝑜𝑟.𝑎𝑠𝑠𝑢𝑚𝑒𝐼𝑠𝑜𝑙𝑎𝑡𝑒𝑑 to provide MainActor context in synchronous methods.

#Swift6 #Concurrency #SwiftConcurrency

3 0 0 0

I believe I must be missing something, but I just have too little experience with #SwiftConcurrency, I guess. 😔
#BuildInPublic #IndieHacker #iOSDev #IndieDev

4 1 1 0
Preview
My (Concurrency) Wishlist for Xcode 27 — I'm Konstantin Swift 6.2 is great and a few qualify of life improvements to Xcode can make it better

Never to early to start writing that wishlist!

#Xcode #Swift #SwiftConcurrency

iamkonstantin.eu/blog/my-conc...

5 2 0 0
Preview
Swift 6 - Sendable, @unchecked Sendable, @Sendable, sending and nonsending Explore how Swift 6 uses Sendable, @Sendable, sending, and nonsending to enforce concurrency safety, ensure thread-safe data transfer, and prevent race conditions.

🧩 Confused by Swift 6 concurrency keywords?
New article breaks down Sendable, `@unchecked Sendable`, `@Sendable`, sending, and nonsending - their differences and use cases.
One table to understand them all 📊
👉 fatbobman.com/en/posts/sen...
#Swift #iOSDev #SwiftConcurrency

1 1 0 0

Why am I even surprised that `NotificationCenter` publishers aren’t updating the UI AHAHAHAHA #swiftConcurrency

1 0 1 0
Original post on hachyderm.io

My talk at OneMoreThing 2024 on #UnitTesting #SwiftUI and #SwiftConcurrency was recorded, but has yet to be edited and uploaded.
Last night, I published an edited form of my speaker notes from that talk to my blog.

blog.rachelbrindle.com/2025/06/12/testing-swift... […]

0 1 0 0
A screenshot showing a type that implements a protocol which includes sendable conformance. You can see that there is a compiler error due to the fact that Sendable cannot be main actor isolated. The type does not have an explicit main actor annotation, because in new projects this is the default.

A screenshot showing a type that implements a protocol which includes sendable conformance. You can see that there is a compiler error due to the fact that Sendable cannot be main actor isolated. The type does not have an explicit main actor annotation, because in new projects this is the default.

A screenshot showing Xcode's project settings and how to change the default actor isolation from main actor back to non-isolated.

A screenshot showing Xcode's project settings and how to change the default actor isolation from main actor back to non-isolated.

Another screenshot from the same type as in the problem scenario, showing that the compiler error is fixed by adding the non-isolated keyword to the type.

Another screenshot from the same type as in the problem scenario, showing that the compiler error is fixed by adding the non-isolated keyword to the type.

📣 #iOSDev PSA: new #Xcode26 projects default to Main Actor isolation, leading to errors with Sendable types ⚠️

Possible Fixes:
1: Change default isolation
2: Mark type nonisolated
3: Ignore #SwiftConcurrency 🫣

💡 Check out @massicotte.org's awesome post:
www.massicotte.org/default-isol...

10 0 2 1
Post image

Don’t miss “What’s New in Swift Concurrency” with Matt Massicotte (@massicotte.org‬) at the One More Thing Conference—this Tuesday at 10 AM! Register now: lu.ma/jhp3xzx6

#SwiftConcurrency #Swift #OMTConf

16 5 0 1
Preview
Behind the scenes of async functions Learn how Swift Concurrency really works

Behind the scenes of async functions
Learn how Swift Concurrency really works

vbat.dev/behind-the-s...

by Vitaly Batrakov
#ios #iosdevelopment #swift #swiftui #swiftlang #SwiftConcurrency #Concurrency

2 0 0 0
The image displays two Swift code snippets illustrating the importance of execution order in asynchronous tasks using `Task.detached`.
First Code Block:
- The task starts by calculating a value (`someValue`) asynchronously using `actor.calculateSomeValue()`, which runs in the background.
- Then, `self.someValueSetter(someValue)` is called to set the value, followed by `actor.someMethod()`, which explicitly runs on the main thread.
Second Code Block:
- The task starts similarly by calculating `someValue` with `actor.calculateSomeValue()` in the background.
- Next, `actor.someMethod()` is executed in the background instead of the main thread.
- Finally, `self.someValueSetter(someValue)` is called to set the value.
The image highlights that the order of operations affects whether certain methods run in the background or on the main thread.

The image displays two Swift code snippets illustrating the importance of execution order in asynchronous tasks using `Task.detached`. First Code Block: - The task starts by calculating a value (`someValue`) asynchronously using `actor.calculateSomeValue()`, which runs in the background. - Then, `self.someValueSetter(someValue)` is called to set the value, followed by `actor.someMethod()`, which explicitly runs on the main thread. Second Code Block: - The task starts similarly by calculating `someValue` with `actor.calculateSomeValue()` in the background. - Next, `actor.someMethod()` is executed in the background instead of the main thread. - Finally, `self.someValueSetter(someValue)` is called to set the value. The image highlights that the order of operations affects whether certain methods run in the background or on the main thread.

Another evening with ModelActor and another strange behavior. This time it's not the way of passing the arguments, but the order of method calling. @massicotte.org, are you interested? 😅
#Swift #ModelActor #SwiftConcurrency

2 0 2 1

I didn’t expect to delve so much into Swift Concurrency at this moment, but it was so interesting investigating what’s working and why I just couldn’t resist. 😅 Don’t get me wrong, I still know very little, but at least I could try to explain the async code I’m writing. 😆
#SwiftConcurrency

1 0 1 0
iOS developers try Swift Structured Concurrency [satire]
iOS developers try Swift Structured Concurrency [satire] YouTube video by Jesse Squires

#SwiftConcurrency

youtu.be/3rNCGFmXvpg

0 0 0 0
A Swift Concurrency Glossary It would be nice if there was a single place to go to look up all the terms, keywords, and annotations related to Swift concurrency. So here it is. By no means do you need to understand everything her...

A Swift Concurrency Glossary

This is a single place where you can find all the terms, keywords, and annotations related to Swift concurrency.

by Matt Massicotte
#ios #iosdevelopment #swift #SwiftConcurrency #swiftlang

www.massicotte.org/concurrency-...

4 0 0 0
Preview
Join the Clipping Camera beta Available on iOS

📸🎨 Release Candidate is ready!

📲 testflight.apple.com/join/aYZWHvK6

It took a while to add the new sementation models and enable #Swift6 😅. #SwiftConcurrency is not AVFoundation friendly… 😒

#BuildInPublic #PhotoArt #ClippingCameraApp #Photography #BackgroundRemoval #PhotoFilters

3 0 0 0

It provides step-by-step guidance for replacing Combine operators like combineLatestand throttle with AsyncAlgorithms equivalents and demonstrates the benefits of simpler, more maintainable code. #ios #iosdevelopment #swift #swiftui #swiftlang #Combine #AsyncAlgorithms #SwiftConcurrency

1 0 0 0

I read these two posts written by @massicotte.org and I feel like this is required reading when migrating to Swift 6 and trying to make full sense of concurrency in that environment.

→ www.massicotte.org/step-by-step...

and

→ www.massicotte.org/step-by-step...

#SwiftLang #SwiftConcurrency

7 0 0 0