Draft guide for id-as-Any migration and known issues

Joe_Groff · August 1, 2016, 6:46pm

Hi everyone. SE-0116 should be landing in snapshots soon, which changes how Objective-C APIs import into Swift. Instead of relying on special implicit conversions to AnyObject, we now import the ObjC APIs using `Any` to get the same effect without special language rules. I've written up a draft guide about the kinds of changes necessary, along with some known issues. I'd also like to gather feedback from anyone who's picked up the snapshot about their experiences to make sure we address any pain points introduced by the changes. Thank you for any feedback you can provide!

-Joe

id-as-Any-migration.md (6.99 KB)

Joe_Groff · August 1, 2016, 11:05pm

I've also posted the document as a gist, to gather updates as I collect them:

gist.github.com

https://gist.github.com/jckarter/5ffa9ba75050b94cd2cf9092b332a866

id-as-Any-migration.md

`id` as `Any`
=============

Swift 3 preview 6 implements the language changes from proposal
[SE-0116](https://github.com/apple/swift-evolution/blob/master/proposals/0116-id-as-any.md), which change the way Objective-C APIs that use `id` are expressed
in Swift to make Swift value types interoperate more naturally with Cocoa
frameworks. The proposal enacts the following changes:

- Swift value types, such as `String`, `Array`, `Dictionary`, and `Set` no longer implicitly convert to the corresponding Cocoa class types `NSString`, `NSArray`, etc.
- Instead, Objective-C APIs with the `id` type now use the `Any` type when used in Swift instead of `AnyObject`. This allows Swift value types to be used seamlessly with these APIs without error-prone implicit conversion behavior affecting the entire language.

This file has been truncated. show original

-Joe

···

On Aug 1, 2016, at 11:46 AM, Joe Groff via swift-users <swift-users@swift.org> wrote:

Hi everyone. SE-0116 should be landing in snapshots soon, which changes how Objective-C APIs import into Swift. Instead of relying on special implicit conversions to AnyObject, we now import the ObjC APIs using `Any` to get the same effect without special language rules. I've written up a draft guide about the kinds of changes necessary, along with some known issues. I'd also like to gather feedback from anyone who's picked up the snapshot about their experiences to make sure we address any pain points introduced by the changes. Thank you for any feedback you can provide!

-Joe

<id-as-Any-migration.md>_______________________________________________
swift-users mailing list
swift-users@swift.org
https://lists.swift.org/mailman/listinfo/swift-users

Honza_Dvorsky1 · August 2, 2016, 7:17am

Thanks Joe!

Does this mean NSJSONSerialization in Foundation will now work with native
Swift dictionaries/arrays? That would be a great if so.

Honza

···

On Tue, Aug 2, 2016 at 1:05 AM Joe Groff via swift-users < swift-users@swift.org> wrote:

I've also posted the document as a gist, to gather updates as I collect
them:

id-as-Any migration and known issues · GitHub

-Joe

> On Aug 1, 2016, at 11:46 AM, Joe Groff via swift-users < > swift-users@swift.org> wrote:
>
> Hi everyone. SE-0116 should be landing in snapshots soon, which changes
how Objective-C APIs import into Swift. Instead of relying on special
implicit conversions to AnyObject, we now import the ObjC APIs using `Any`
to get the same effect without special language rules. I've written up a
draft guide about the kinds of changes necessary, along with some known
issues. I'd also like to gather feedback from anyone who's picked up the
snapshot about their experiences to make sure we address any pain points
introduced by the changes. Thank you for any feedback you can provide!
>
> -Joe
>
> <id-as-Any-migration.md>_______________________________________________
> swift-users mailing list
> swift-users@swift.org
> https://lists.swift.org/mailman/listinfo/swift-users

_______________________________________________
swift-users mailing list
swift-users@swift.org
https://lists.swift.org/mailman/listinfo/swift-users