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

[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] NSTask and try!

2016-05-13 Thread James Lee via swift-corelibs-dev
when an error is thrown with a try! but fail on OSX Sent from my iPhone > On 13 May 2016, at 20:48, Tony Parker wrote: > > Hi James, > >> On May 13, 2016, at 12:25 PM, James Lee via swift-corelibs-dev >> wrote: >> >> Following on from a previous discussi

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

2016-05-14 Thread James Lee via swift-corelibs-dev
we’re > abstracting is significantly different, so I’m not too surprised. > > > > We should try to get something in place so we’re not failing on OS X in the > short term for sure. > > > > - Tony > > > > Sent from my iPhone > > > >

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

2016-05-14 Thread James Lee via swift-corelibs-dev
Cheers for the clarification. I will spend some time working through some of the other failures, should help me get to grips with it all :) James Sent from my iPhone > On 14 May 2016, at 15:02, Bouke Haarsma via swift-corelibs-dev > wrote: > > On 2016-05-14 09:05:08 +0000, J