[swift-corelibs-dev] Better integration with UNIX tools

Tony Parker anthony.parker at apple.com
Tue Nov 28 10:00:10 CST 2017

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 <brent at architechies.com> wrote:
>> On Nov 27, 2017, at 11:01 PM, Brent Royal-Gordon <brent at 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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-corelibs-dev/attachments/20171128/70c8c0b8/attachment.html>

More information about the swift-corelibs-dev mailing list