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

Hi David, > On May 14, 2016, at 1:04 AM, David Hart wrote: > > Thanks for all the answers :) These questions are dear to my heart because I > plan on using corelibs-foundation on Darwin as soon as possible to share code > between our iOS apps and web services. Yup, that

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

> On 14 May 2016, at 01:39, Tony Parker wrote: > > No. Only on Linux or other non-Darwin platforms. Ok, I understand that corelibs won't be the official "Foundation" framework on Darwin, but it will still be available under SwiftFoundation without having to compile

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

Thanks for all the answers :) These questions are dear to my heart because I plan on using corelibs-foundation on Darwin as soon as possible to share code between our iOS apps and web services. > On 14 May 2016, at 01:39, Tony Parker wrote: > > Over time it’s not

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] 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] 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

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

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, Status and Know Issues docs have not been updated in a very long time, as if abandoned. Hopefully we can