Lmst

🗓️ Saturday, July 5, 11:30am Pacific, 18:30 UTC
Swift Concurrency, Group Learning Session: Parallelization of Tasks

In this session, we will be investigating and leveraging parallelization of tasks. Specifically, we will attempt to parallelize rendering of map tiles in the CubiomesKit project.
#SwiftConcurrency #SwiftDev #AppleDev
https://discord.gg/euyXVzzX?event=1388624765169827942

🗓️ Saturday, July 5, 11:30am Pacific, 18:30 UTC
Swift Concurrency, Group Learning Session: Parallelization of Tasks

In this session, we will be investigating and leveraging parallelization of tasks. Specifically, we will attempt to parallelize rendering of map tiles in the CubiomesKit project.
#SwiftConcurrency #SwiftDev #AppleDev

https://discord.gg/nyXRvBC5tS?event=1388624765169827942

✨Swift 6.2 ✨

SE-0481 is introducing "weak let" to Swift 6.2!

That will allow us to create immutable weak references that can't be reassigned after initialization, but can still become nil when the referenced object is deallocated.

This is a game-changer for Sendable compliance (weak var can't be Sendable, but weak let can!) 🎉

#Swift #iOS #SwiftConcurrency #SwiftLang

https://github.com/swiftlang/swift-evolution/blob/main/proposals/0481-weak-let.md

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.

https://blog.rachelbrindle.com/2025/06/12/testing-swiftui-and-swiftconcurrency/

#SwiftLang

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

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

@mattiem has a great post on default isolation: https://www.massicotte.org/default-isolation-swift-6_2

Quite frankly, if I hadn't read your post before, I probably would've taken a lot longer to figure out why the heck the type in question was MainActor isolated to begin with - thanks Matt! 👏

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.

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.

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

#SwiftConcurrency #Swift #OMTConf

🚨 New Premium Workshop!

“Concurrency Fundamentals with Swift 6.2”
w/ @mattiem
🗓️ Sunday, June 8 | 🕐 1–4 PM
📍 Cupertino, CA
🎟️ Sign up: https://buff.ly/R921TWg

Matt Massicotte has taught private workshops for over 60 engineers, and his contributions to Swift Concurrency are widely respected by Apple devs.

Best of all, Matt is generously donating all proceeds to support OMT’s free community programming throughout WWDC week ❤️

#SwiftLang #Swift #AppleDev #SwiftConcurrency #WWDC25

🗓️ Next Saturday, June 7, 11:30am Pacific, 18:30 UTC
Group-learning session focused on use of actors in Swift Concurrency.

#SwiftConcurrency #SwiftDev #iosDev #macOSDev
On the Swift Dev Chat Discord:
https://discord.gg/sGM552KyMn?event=1378456030488301598

Reminder: Group learning session on the Swift Dev Chat Discord server.
🗓️ This Saturday, May 24, 11am Pacific, 18:00 UTC.

Participate in “ensemble coding” as we (try to) apply strict Swift Concurrency to an existing open source project (XcInspector—SwiftUI app on macOS, plus command-line tool).
All experience levels welcome—as long as you’re wanting to learn more about programming in Swift.
#SwiftUI #SwiftConcurrency
https://discord.gg/sGM552KyMn?event=1370844232952053852

Group learning session on the Swift Dev Chat Discord server.
🗓️ Saturday, May 24, 11am Pacific, 18:00 UTC.

Participate in “ensemble coding” as we (try to) apply strict Swift Concurrency to an existing open source project (XcInspector—SwiftUI app on macOS, plus command-line tool).
All experience levels welcome—as long as you’re wanting to learn more about programming in Swift.
#SwiftUI #SwiftConcurrency
https://discord.gg/sGM552KyMn?event=1370844232952053852

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. @mattiem, are you interested? 😅
#Swift #ModelActor #SwiftConcurrency

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.

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 #iOSProgramming

At https://talk.objc.io/ I’ve found a series about Swift 6 Concurrency, see here. I’m going to read/watch the episodes since my Swift knowledge is still on Swift 5.9.
#swift #swiftlang #swiftconcurrency #swift6 #swift6concurrency
@swift

My app, #PDXTransit, turns 10 years old this year this August. I wrote it when I moved to Portland back in 2015.

Well, this year for its 10th birthday, I plan to release a complete re-write using the latest technologies from Apple including an iPad-specific user experience.

Here's a sneak peek at what I've been working on the past few years with #SwiftUI, #SwiftConcurrency, and #SwiftData!!!

(and of course it comes with a re-write of its companion app for Apple Watch!)

#TriMet #Portland

💡 Swift Concurrency has different flavors of tasks, each with its own behavior for lifetime, cancellation, and inheritance.

This cheat sheet is pretty cool for quick reference! 🚀

https://forums.swift.org/t/understanding-task-cancellation/75329

#iOSDev #Swift #swiftconcurrency

That's a handy reference!

#Swift #SwiftConcurrency
https://mastodon.social/@mjtsai/113949266898144702

Swift Concurrency question. I'm trying to get a replacement for Combine's CurrentValueSubject to work but no luck. Any ideas?

You know... Actor-isolated instance method 'makeAsyncIterator()' cannot be used to satisfy nonisolated protocol requirement.

I think I can put a Task into the continuation Callback, but is it a good idea?
#swiftconcurrency #swift

Whew! Over two hundred #swiftconcurrency warnings/errors taken care of, with only one dubious use of unchecked sendable.

I did not know that turning on "Strict Concurrency Checking" (without changing swift version) could change the actual runtime instead of just compile-time warnings. Found a bug that was driving me crazy (FB15391171).

Xcode 16 Beta 1 + Strict Concurrency on: `async let`, when ran on a synchronous function, runs on the current actor instead of the expected background executor. Does not happen on 16. It's one of those "is my mental model wrong again" bugs 😅 #swiftconcurrency

Getting Ready for Swift 6 https://www.youtube.com/live/kc-a8_DFXgE?si=bebLC1f3esp920sZ&t=3217 @ktoso #Swift #Swift6 #SwiftConcurrency

#swiftconcurrency

Client Info