> 1. Integrate swift-corelibs-dispatch into Foundation.
Are there any lingering items in swift-corelibs-dispatch that are still pending
full implementations on either Darwin or Linux?
Dan
___
swift-corelibs-dev mailing list
swift-corelibs-dev@swift.org
While we’re on the subject, I’ve been out of the loop for a little while: how’s
the Linux-side implementation of dispatch sources looking these days? In
particular, I’m interested in the status of DISPATCH_SOURCE_TYPE_READ and
DISPATCH_SOURCE_TYPE_PROC.
Right now, NSTask is using Good Ol’ CFRu
Hey Alexander,
I supplied most of the initial implementation of NSTask, but was holding off on
IO redirection until someone tackled NSFileHandle. I can’t say if anyone else
on this list is working on this right now, but if not and if you’re really
interested in finishing NSFileHandle, I would
I'm trying to invoke Linux's unshare() system call from Swift, but without much
success. From C, it requires _GNU_SOURCE to be #define'd before the #include
. The Glibc module map does indeed include sched.h, so the lack of
_GNU_SOURCE appears to be the likely culprit. What's the appropriate
ind of awful. I'm not up
>> to date on what the best approach to use for this on Linux would be; it
>> sounds like clone() can do it, but I don't know if that's exposed at the
>> posix_spawn level at all.
>>
>> David
>>
>>> On Dec 18,
I hope to take a crack at implementing some of NSTask this weekend. What are
the recommended posix_spawnattr_t flags that should be set? Do we also want to
take the opportunity to expose the ability to override some of these flags
(like POSIX_SPAWN_SETPGROUP) or do we want to avoid tying this
NSTask, it sure seems like we
> only expect either a file handle or pipe. I’m not sure if we would ever add
> another.
>
> - Tony
>
>> On Dec 17, 2015, at 11:34 AM, Dan Stenmark via swift-corelibs-dev
>> mailto:swift-corelibs-dev@swift.org>> wrote:
>>
This is my first proposal to swift-corelibs, so I’m not sure how much
flexibility we have in terms of deviating from the darwin’s original Foundation
definitions. That said, it’s always seemed a little screwy to me that NSTask's
standardInput/standardOutput/standardError properties sacrifice an
