[swift-evolution] [Pitch] Importing Objective-C 'id' as Swift 'Any'
shawnce at gmail.com
Sat Jul 2 08:53:24 CDT 2016
It does look like a huge benefit for many many current swift users. Thanks
to the whole team trying to make this happen in Swift 3.
On Fri, Jul 1, 2016 at 10:21 PM 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:
> > +1!
> > 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
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the swift-evolution