Re: [swift-corelibs-dev] Looking at corelibs-foundation

> On May 13, 2016, at 4:13 PM, David Hart wrote: > > Hi Tony, > > I’m a bit confused by your answer. I am aware that some Objective-C > Foundation and swift-corelibs-foundation classes share a common > implementation through CF. My questions were really about the place of

Re: [swift-corelibs-dev] Looking at corelibs-foundation

Hi Tony, I’m a bit confused by your answer. I am aware that some Objective-C Foundation and swift-corelibs-foundation classes share a common implementation through CF. My questions were really about the place of swift-corelibs-foundation on OS X and iOS. Can you help me understand? What did

Re: [swift-corelibs-dev] Looking at corelibs-foundation

Hi David, Much of the implementation is indeed shared (via the CoreFoundation C code, and the stuff it uses like ICU and libdispatch). Some of it is a reimplementation of the same API, but in Swift. If you write code targeting the Foundation API, then you simply ‘import Foundation’. The idea

Re: [swift-corelibs-dev] Looking at corelibs-foundation

> On 13 May 2016, at 21:50, Tony Parker wrote: > > Technically, swift-corelibs-foundation is only part of the distribution on > Linux. On Darwin platforms, we use a combination of the overlay > (stdlib/public/SDK/Foundation directory in the Swift project) and the >

Re: [swift-corelibs-dev] NSTask and try!

> On May 13, 2016, at 1:05 PM, James Lee wrote: > > Cheers for the clarification. I started assuming there may be a reason when > changing the guard let on the launch args to use the InvalidArgumentException. > > Could this be a position where we may need os checking to

Re: [swift-corelibs-dev] NSTask and try!

Cheers for the clarification. I started assuming there may be a reason when changing the guard let on the launch args to use the InvalidArgumentException. Could this be a position where we may need os checking to cover the regression for the moment. It seems odd that the test would pass in CI

Re: [swift-corelibs-dev] Looking at corelibs-foundation

> On May 13, 2016, at 10:33 AM, Rob Allen wrote: > > Hi all, > >> On 13 May 2016, at 18:01, Tony Parker via swift-corelibs-dev >> > wrote: >> >> Hi David, >> >>> On May 11, 2016, at 4:02 PM, David Hart via

Re: [swift-corelibs-dev] NSTask and try!

Hi James, > On May 13, 2016, at 12:25 PM, James Lee via swift-corelibs-dev > wrote: > > Following on from a previous discussion with Tests failing on OSX. I have > been looking into the failures. It seems that one of the earliest failures is > due to an error

[swift-corelibs-dev] NSTask and try!

Following on from a previous discussion with Tests failing on OSX. I have been looking into the failures. It seems that one of the earliest failures is due to an error from a try! within NSTask.launch(). This came in with this commit:

Re: [swift-corelibs-dev] Looking at corelibs-foundation

Hi all, > On 13 May 2016, at 18:01, Tony Parker via swift-corelibs-dev > wrote: > > Hi David, > >> On May 11, 2016, at 4:02 PM, David Hart via swift-corelibs-dev >> > wrote: >> >> Hello people,

Re: [swift-corelibs-dev] Looking at corelibs-foundation

I did this search to try and find some: https://github.com/apple/swift-corelibs-foundation/pulls?utf8=✓=is%3Apr+is%3Aclosed+is%3Aunmerged Here’s one:

Re: [swift-corelibs-dev] Looking at corelibs-foundation

Wanted to chirp up and say I am in the same position as David, with that said, if PR's have been rejected due to a lack of response, are there any that have not been covered elsewhere and can be picked up? James Sent from my iPhone > On 13 May 2016, at 18:01, Tony Parker via

Re: [swift-corelibs-dev] Looking at corelibs-foundation

Hi David, > On May 11, 2016, at 4:02 PM, David Hart via swift-corelibs-dev > wrote: > > Hello people, > > I wanted to start giving a hand on corelibs-foundation but hit two obstacles > I’d like to discuss: > > It feels difficult to know where help is needed