Re: [swift-corelibs-dev] Migrate corelibs-foundation to the newest APIs

1 >> Date: Tue, 12 Apr 2016 09:57:38 -0700 >> From: Tony Parker > <mailto:anthony.par...@apple.com>> >> To: Robert F Dickerson > <mailto:rfdicker...@us.ibm.com>> >> Cc: swift-corelibs-dev@swift.org <mailto:swift-corelibs-dev@swift.org> >> Sub

Re: [swift-corelibs-dev] Migrate corelibs-foundation to the newest APIs

com/apple/swift-corelibs-foundation/pull/317> - Bhaktavatsal > Message: 1 > Date: Tue, 12 Apr 2016 09:57:38 -0700 > From: Tony Parker > To: Robert F Dickerson > Cc: swift-corelibs-dev@swift.org > Subject: Re: [swift-corelibs-dev] Migrate corelibs-foundation to the >

Re: [swift-corelibs-dev] Migrate corelibs-foundation to the newest APIs

I noticed the folks at IBM were also doing platform checks when using the corelibs-xctest APIs. I created https://bugs.swift.org/browse/SR-1215 to track the issue. corelibs-xctest is small enough that we may want to consider providing *both* Swift 2.2 and Swift 3 APIs, perhaps behind a `#if swift(

Re: [swift-corelibs-dev] Migrate corelibs-foundation to the newest APIs

Hi Robert, This is something we really do need some help with. Our goal is to have the Linux version match the Darwin version exactly. There is also a PR up to change some of the results of the automatic renaming by the importer, here: https://github.com/apple/swift/pull/2093

[swift-corelibs-dev] Migrate corelibs-foundation to the newest APIs

As you know, currently, as of the 03-24 DEVELOPMENT snapshot, the function signatures for Foundation has diverged. This has caused us to create platform specific calls to the NSString, NSDate, NSCache, etc. classes. For instance,