Re: [swift-corelibs-dev] Wrapping up Swift 3 for swift-corelibs

M Subject: Re: [swift-corelibs-dev] Wrapping up Swift 3 for swift-corelibs Sent by:daniel_dun...@apple.com Can someone file a bug to track how we are going to resolve this issue, and outline our options? I want to make sure we have enough eyes on it to make sure we get what we

Re: [swift-corelibs-dev] Wrapping up Swift 3 for swift-corelibs

I think a future release is prudent, for the following reasons: 1. swift-corelibs-xctest requires users to list each of their tests in an `allTests` static property. However, this isn't source-incompatible with Darwin XCTest. A developer could include the list on Darwin, and their tests would

Re: [swift-corelibs-dev] Wrapping up Swift 3 for swift-corelibs

Hm, I’ll have to defer to Mike on the status of this one. If it’s not in place now, we should probably schedule it for a future release. - Tony > On Jul 29, 2016, at 11:43 AM, Brian Gesiak wrote: > > Thanks for the heads up, Tony! > > (+cc corelibs-xctest release manager

Re: [swift-corelibs-dev] Wrapping up Swift 3 for swift-corelibs

Hi Gonzalo, While not a complete solution for the issues around bridging, the work on id-as-Any that I mentioned below was meant to help address these platform differences. For example, let’s say you had a Foundation API that looked like this in ObjC: - (void)foo:(id)x; and imported like