What’s next for Foundation

[Geordie_J (ephemer)]

Thanks @ktoso for your reply! I’m not sure I understand the idea about using a custom clock. I don’t think I need a specific type of timing, I’d just like to ensure that Task.sleep works with the suggestion I made above (and maybe get some tips on how this works otherwise if it doesn’t). I will have to try it and see I guess.

I agree that it’d be nice to have a separate thread about this. I actually tried starting two separate threads about this recently but didn’t get any response:

[Prepitch] Using @MainActor and DispatchQueue.main.async without Foundation

We currently use DispatchQueue.main... and @MainActor a lot throughout our codebases on non-Darwin platforms. Since we need to interact with the "real" main thread on platforms like Android, it's important to us that these "main thread" things really do run on the main thread. However, we cannot take over the main thread entirely via something like CFRunLoopRun() or dispatch_main() etc., because then the entire process will essentially freeze. i.e., we need to cooperate with the process' existi…

Draining DispatchQueue.main without overtaking the main thread (and without Foundation)

@MainActor annotations and DispatchQueue.main... only work if something is draining the main dispatch queue. Normally, calling RunLoop.main.run() or dispatchMain() on the main thread would be enough to solve this. The problem is, those those functions return Never, meaning if you have something else on the main thread that isn't using Dispatch etc., your environment will hang. This is notably the case on Android when running native Swift code within Java/Kotlin apps, which have their own run loo…

Not sure if I posted those in the wrong place or something but if neither of those topics are appropriate I’d be happy to start another The conversation here has certainly changed my mindset about what the correct approach would be; another difference is that Dispatch is out of the picture now too.