Interesting, I've wrapped some code in `Task { @MainActor in /* code */ }` because I wanted to hide the concurrency warning, and now my app is way faster. I've no idea how, but I'm happy that this is the effect #swiftlang #concurrency #swift #mainactor #task #indiedev

This Swift 6 code crashes in _dispatch_assert_queue_fail(), even if the installTap() closure is empty. If I remove the MainActor annotation on the class, it works. Anybody else seen and/or worked around this?

The #Interaction and #Concurrency Experience #workshop (ICE ) 2025 Call for paper is out! #CFP https://ice-workshop.github.io/cfp.txt

ICE will be co-located with @DisCoTecConf and take place in #Lille , #France on June 16th (https://www.discotec.org/2025/satellite/ice).

This workshop is very dear to me: instead of the usual "submission ⇉ (rebuttal ⇉) review" flow, it uses a very original selection procedure (https://www.discotec.org/2025/satellite/ice#the-ice-selection-procedure), where PC members and authors discuss and collaborate for the greater good ⇆.

This year again we have an amazing program committee (https://www.discotec.org/2025/satellite/ice#programme-committee), an amazing invited speaker (Kirstin Peters, from Augsburg University) and welcome submissions until April 9th, 2025 .

There are an indeterminate number of wolves inside of you. One has a large patch to apply, and the others have a steady stream of small patches to apply. All patches must be rebase-clean before they apply for audit reasons.

The probability of the wolves livelocking asymptotically approaches 1.

Preventing data races with Pony

https://lwn.net/SubscriberLink/1001224/25f4c02cdb2a432e/

#Swift #Concurrency

Has something changed in concurrency warnings between Xcode 16.1 and Xcode 16.2 beta 3? Here is an example of a warning that I get in 16.1 but not 16.2b3. (I think not getting it is correct?) I can’t find any release notes or such about this.

(I put such explicit captures there because 16.2b3 was warning about implicit captures.)

#Swift #Concurrency #AsyncStream

I think I’m slowly starting to develop some intuition for how to work with Swift concurrency

I encountered a warning when working on a seemingly simple problem: how do you convert an array to AsyncStream

My solution with an actor compiles without warnings and makes sense to me, but is there some even simpler way?

#Swift #APNS #Concurrency

Is there any sane way to make this warning go away, other than using the older callback-based method of this API?

#Swift #Concurrency #Combine

Here is August 2024

And I still sadly find myself writing new code in Combine

Because modern async stream does not support multicast

Another day, another #Swift #Concurrency question. How would I fix this? #UIKit #SwiftUI

Any idea how to fix this warning? #SwiftUI #UIKit #Swift #Concurrency

#SwiftData #Concurrency

I’m toying around with SwiftData a bit. One thing I don’t understand: when I try do offload work into background, why does it end up back on the main thread here?

I call this with Task {} from UI.

Shouldn’t ModelActor make sure it ends up on some background thread? What am I missing?

My worry with the “Swift 5 is not going anywhere” argument is that many upcoming features will be soon available on Swift 6 exclusively and most developers will be forced to immaturely upgrade just to have access to them. I just found out that Typed Throws is only available on 6 for some reason and I am both frustrated and pissed!

Can anyone recommend a tutorial or blog series that goes through the whole modern #Swiftlang #concurrency story in a progressive manner, taking it through through from the basics to the latest Swift 6 considerations.
I've been using it for the last couple of years but it feels like using a set of known patterns but without a deep understanding of detail and theory behind the patterns … and it is not a situation I’m comfortable with.

Generic Concurrency in Go
https://sergey.kamardin.org/articles/generic-concurrency-in-go/ #Golang #Concurrency

Is there a safe way to use #AVCaptureSession with #swift strict #concurrency checking enabled? It's not Sendable, but the documentation clearly states that `startRunning()` is a blocking call and should not be called from the main queue.

I'm available to jump in fast, remotely, for paid work doing Golang or C programming, for Linux or Mac. or doing performance/scaling fixes/tuning/upgrades

programming for decades. senior. tech team leadership & R&D mentality. a human engine who churns out new code, solves problems & ships. Heisenbugs too are my jam

I want to have the biggest impact I can have for you, while also using time efficiently

#fedihire

#Golang
#C
#Linux

#performance
#scalability
#latency
#concurrency
#threading

#SwiftUI #Concurrency

Why is Swift(UI) complaining when listening for asyncsequence in a SwiftUI view task modifier? Is this some kind of antipattern? How am I supposed to do this without warnings?

#introduction

I’m on Mastodon for two things.

I build things on Apple platforms. I make @tact. I read (a lot) and post (a little) about related technologies: #Swift, #SwiftUI, #Combine, #CloudKit, #CoreData, #Xcode, #concurrency, as well as product design.

I support Ukraine. I follow Ukrainians and friends of . Please donate to until is gone: https://u24.gov.ua or any other respected charity. My Twitter is mostly about Ukraine - https://twitter.com/jaanus