<font size=2 face="sans-serif">Is there a view (yet) on if/when/how the
"Swift" implementation of Foundation will be used on Darwin?</font>
<br>
<br><font size=2 face="sans-serif">Currently under TestFoundation, the
"Swift" version is its imported as SwiftFoundation on Darwin.
Is the medium/long term view? ie, that the Swift implementation will be
"SwiftFoundation", with function renaming done to drop the "NS",
thereby allowing developers to keep their existing applications on the
Obj-C implementation, or consciously decide to migrate to the Swift version?
</font>
<br>
<br><font size=2 face="sans-serif">Thanks,</font>
<br>
<br><font size=2 face="sans-serif">Chris<br>
</font>
<br>
<br>
<br>
<br><font size=1 color=#5f5f5f face="sans-serif">From:
</font><font size=1 face="sans-serif">Philippe Hausler via
swift-dev <swift-dev@swift.org></font>
<br><font size=1 color=#5f5f5f face="sans-serif">To:
</font><font size=1 face="sans-serif">Mike Berg <mberg@solstice-consulting.com></font>
<br><font size=1 color=#5f5f5f face="sans-serif">Cc:
</font><font size=1 face="sans-serif">Justin Baumgartner
<jbaumgartner@solstice-consulting.com>, swift-dev@swift.org</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Date:
</font><font size=1 face="sans-serif">22/04/2016 22:36</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Subject:
</font><font size=1 face="sans-serif">Re: [swift-dev]
Libraries written in Objective-C in Swift 3</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Sent by:
</font><font size=1 face="sans-serif">swift-dev-bounces@swift.org</font>
<br>
<hr noshade>
<br>
<br>
<br><tt><font size=2><br>
> On Apr 22, 2016, at 2:03 PM, Mike Berg via swift-dev <swift-dev@swift.org>
wrote:<br>
> <br>
> Hi everyone,<br>
> <br>
> A question has come up on my project that nobody seems to have an
answer for. I was hoping someone here might know:<br>
> <br>
> On my project, we have a longstanding iOS application that has both
objC and swift source files. As is the case for most old apps out there
(a few years), we regularly use swift code in objC and vice versa.<br>
> <br>
> We have been keeping tabs on how Swift has been expanding and we noticed
that with Swift 3, the foundation classes will be rewritten in swift. So
does this mean that all Swift classes using Foundation automatically start
using Foundation written in Swift or is it opt-in? If it’s mandatory,
then will libraries dependent on the Objective-C runtime no longer work
(i.e. the Alamofire git repo)?<br>
<br>
The foundation classes are not being re-written in Swift (for Darwin, the
linux versions however are). The current proposal on the evolution list
is for structures, which act in parallel to their reference type counterparts.
You can still use a reference type where it makes sense, but now you can
use a struct type where that is desired for a few new types.<br>
<br>
One slight change that might have some effect is how the APIs are imported.
If an API exposed a return type of NSData now it will return a struct Data.
That can easily be converted back via using `as NSData`.<br>
<br>
> <br>
> Thanks for reading and take care,<br>
> -- <br>
> Michael Berg<br>
> Technical Analyst<br>
> Solstice Mobile<br>
> (630) 414-6938<br>
> _______________________________________________<br>
> swift-dev mailing list<br>
> swift-dev@swift.org<br>
> </font></tt><a href="https://lists.swift.org/mailman/listinfo/swift-dev"><tt><font size=2>https://lists.swift.org/mailman/listinfo/swift-dev</font></tt></a><tt><font size=2><br>
<br>
_______________________________________________<br>
swift-dev mailing list<br>
swift-dev@swift.org<br>
</font></tt><a href="https://lists.swift.org/mailman/listinfo/swift-dev"><tt><font size=2>https://lists.swift.org/mailman/listinfo/swift-dev</font></tt></a><tt><font size=2><br>
</font></tt>
<br>
<br>