<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div><blockquote type="cite" class=""><div class="">On Dec 21, 2017, at 10:57 AM, Geordie J via swift-corelibs-dev <<a href="mailto:swift-corelibs-dev@swift.org" class="">swift-corelibs-dev@swift.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html; charset=utf-8" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Hi,<div class=""><br class=""></div><div class="">We are having some issues with threading / dispatch queues this week. Basically I’m wondering why the following “async” code has the output it does:</div><div class=""><br class=""></div><div class=""><i class="">print(Thread.isMainThread) // true</i></div><div class=""><i class="">DispatchQueue.main.<b class="">async</b> {</i></div><div class=""><i class=""> print(Thread.isMainThread) // false (???)</i></div><div class=""><i class="">}</i></div></div></div></blockquote><div><br class=""></div><div>This is wrong.</div><br class=""><blockquote type="cite" class=""><div class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div class=""><br class=""></div><div class="">Whereas this same code but with “sync" prints “true” “true”:</div><div class=""><br class=""></div><div class=""><div class=""><i class="">print(Thread.isMainThread) // true</i></div><div class=""><i class="">DispatchQueue.main.<b class="">sync</b> {</i></div><div class=""><i class=""> print(Thread.isMainThread) // true</i></div><div class=""><i class="">}</i></div></div></div></div></blockquote><div><br class=""></div><div>This is expected, because dispatch_sync() on the main thread is... difficult.</div><br class=""><blockquote type="cite" class=""><div class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div class=""><br class=""></div><div class="">This goes against what I thought I understood about Dispatch. Are there any threading guarantees made by DispatchQueue at all? Especially on the main queue. And if not, is there another construct we can use?</div><div class=""><br class=""></div><div class="">The issue is that we’re on Android (where the threading situation is cloudy at best to begin with) and the JNI (Java-Native Interface) has specific requirements about which threads its methods are run on. Let alone our graphics rendering code.</div><div class=""><br class=""></div><div class="">Basically, initialising and using the JNI in separate DispatchQueue.main.async blocks apparently does not end up on the same thread (and apparently neither of them are the main thread). I’m quite confused by this.</div><div class=""><br class=""></div><div class="">Are there any resources or docs to get up to scratch with the internals of Dispatch a bit better?</div></div></div></blockquote><div><br class=""></div><div>THe problem here is not Dispatch, it's how it's (mis-)ported to Android for now.</div><div><br class=""></div><div>On other platforms, either you call dispatch_main() and there's no main thread anymore, or from the main thread you are supposed to drain the Main CFRunloop which in turn is integrated with dispatch (or rather the other way around: dispatch is integrated with the main CFRunloop) and the main queue acts as a source on the main CFRunloop.</div><div><br class=""></div><div>Last I heard, Android has not done that. I tried to explain this on <a href="https://github.com/apple/swift-corelibs-libdispatch/pull/299" class="">https://github.com/apple/swift-corelibs-libdispatch/pull/299</a> which atm is still not resolved.</div><div><br class=""></div><div>-Pierre</div></div></body></html>