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

2016-05-13 Thread Tony Parker via swift-corelibs-dev
> 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 > swift-corelibs-fo

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

2016-05-13 Thread David Hart via swift-corelibs-dev
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 yo

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

2016-05-13 Thread Tony Parker via swift-corelibs-dev
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 h

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

2016-05-13 Thread David Hart via swift-corelibs-dev
After looking into it, I guess it would be available, but under the SwiftFoundation module. Correct? I guess that decision was made so that Swift apps in production built on Foundation don’t break when recompiled under Swift 3? Is it worth converging the names of the module so its the same on al

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

2016-05-13 Thread David Hart via swift-corelibs-dev
> 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 > Foundation.framework that s

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

2016-05-13 Thread Tony Parker via swift-corelibs-dev
> 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 cover the > regression

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

2016-05-13 Thread James Lee via swift-corelibs-dev
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 wh

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

2016-05-13 Thread Tony Parker via swift-corelibs-dev
> 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 >> mailto:swift-corelibs-dev@swift.org>> wrote: >> >> Hi David, >> >>> On May 11, 2016, at 4:02 PM, David Hart via swift-corelibs-dev >>> mailto:swift-corelibs-dev@

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

2016-05-13 Thread Tony Parker via swift-corelibs-dev
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 from a try! within NSTask.launch(

[swift-corelibs-dev] NSTask and try!

2016-05-13 Thread James Lee via swift-corelibs-dev
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: https://github.com/apple/swift-corelibs-foundation/commit/4c

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

2016-05-13 Thread Rob Allen via swift-corelibs-dev
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 >> mailto:swift-corelibs-dev@swift.org>> wrote: >> >> Hello people, >> >> I wanted to start giving a hand on corelibs-foundation

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

2016-05-13 Thread Tony Parker via swift-corelibs-dev
I did this search to try and find some: https://github.com/apple/swift-corelibs-foundation/pulls?utf8=✓&q=is%3Apr+is%3Aclosed+is%3Aunmerged Here’s one: https://github.com/apple/swift-corelib

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

2016-05-13 Thread James Lee via swift-corelibs-dev
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 swift-corelibs-dev

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

2016-05-13 Thread Tony Parker via swift-corelibs-dev
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 because the ReleaseNotes, > Statu