[swift-evolution] [Pitch] Importing Objective-C 'id' as Swift 'Any'
panajev at gmail.com
Sat Jul 2 03:20:38 CDT 2016
Do you have plans to allow people to update Swift outside Xcode 8 point updates and still be able to submit to the App Store and benefit from the IDE's features? This could allow bug fixes to be delivered on a swifter way and take advantage of the fact that iOS is not including the runtime yet.
Sent from my iPhone
> On 2 Jul 2016, at 06:21, Chris Lattner via swift-evolution <swift-evolution at swift.org> wrote:
>> On Jul 1, 2016, at 9:11 PM, David Waite via swift-evolution <swift-evolution at swift.org> wrote:
>> To me, it feels like the ambivalent dynamic casting is a temporary complexity, and that at some point in the future the need to expose legacy reference types like NSString outside swift-supplied or user-created bridging code will disappear completely.
>> This also will get rid of some of the rough edges in the various corelibs where value types cannot be supported because some platforms have a backing library written in Objective-C. Swiftier indeed!
>> Is this something you are pushing for in Swift 3? It seems appropriate but ambitious.
> Yes, we’re trying for it. “Appropriate but ambitious” is an accurate assessment - this is a huge stretch by the entire team but Swift 3 is the right time for it.
> swift-evolution mailing list
> swift-evolution at swift.org
More information about the swift-evolution