Why does it imply a run loop rather than one of many multithreading possibilities (dispatch queue, starting one more thread, etc)? And even if it did use run loops, why is that a problem?
In general we have been discouraging the use of synchronous and blocking API for many years now. It’s convenient for a script like this, but the API under discussion would be available to all kinds of apps. We must look for a solution that is general enough to be useful everywhere. - Tony > On Nov 27, 2017, at 11:50 PM, Brent Royal-Gordon <br...@architechies.com> > wrote: > >> On Nov 27, 2017, at 11:01 PM, Brent Royal-Gordon <br...@architechies.com> >> wrote: >> >> We aren't today > > > Sorry, this part of the sentence got mangled in editing. What I meant to say > is, script-style programs currently don't run under a runloop, so if this API > is being designed for scripting use, a completion handler—even with > async/await—might not be the right design. > > -- > Brent Royal-Gordon > Architechies >
_______________________________________________ swift-corelibs-dev mailing list swift-corelibs-dev@swift.org https://lists.swift.org/mailman/listinfo/swift-corelibs-dev
