helge, 11 months ago

@ctietze As discussed elsewhere 🙈 Thread + RunLoop is one thing you can do.

ctietze, 11 months ago

@helge I guess that was discarded by someone else already then :D

mattiem, 11 months ago

@ctietze with concurrency?

ctietze, 11 months ago

@mattiem with whatever it takes :)

mattiem, 11 months ago

@ctietze with concurrency requires custom executors, which is new and I’m not sure what the availability is.

Without concurrency, though, shouldn’t be any different that ObjC. Is it?

ctietze, 11 months ago

@mattiem Yeah, I never worked with NSRunLoop + NSThread isolation in the past, but this old Realm article looks ok: https://academy.realm.io/posts/realm-notifications-on-background-threads-with-swift/

mattiem, 11 months ago

@ctietze I would be very interested if you opted to go for the custom executor path, and I'd even offer to help a bit! But, I bet avoiding it is more practical.

icanzilb, 11 months ago

@mattiem @ctietze lol I wouldn't trust that guy who wrote the article, what does he know 😂

icanzilb, 11 months ago

@mattiem @ctietze apropos if you're copying this code I remember there might've been an issue picking between distant future or past for the runloop run, but can't remember details right now

ctietze, 11 months ago

@icanzilb @mattiem :blobcatcoffee: thanks

ctietze, 11 months ago (edited 11 months ago)

@mattiem Thank you for the offer! Favored solution 100%, but it's maybe not backdeployed, maybe it is, so not sure if we can wait for Xcode 15 RC 🤷‍♂️ @oliep

helge, 11 months ago

@mattiem @ctietze People say the executors require macOS 14+. But yes, otherwise same situation as in ObjC.

icanzilb, 11 months ago

@helge @mattiem @ctietze executors were available from start, just that you were not able to create new ones so maybe they backported the new parts? I'm also curious but have no time to check 😬

ctietze, 11 months ago

@icanzilb @helge @mattiem https://github.com/apple/swift/blob/0f201443acf3b12975b63a49611dea8131c007df/stdlib/public/BackDeployConcurrency/Actor.cpp

I don't know exactly what I'm seeing, but it kinda sorta looks like it's not tied to macOS 14, maybe?