04: Bridging with Objective-C

Swift Unwrapped

Content provided by Spec Network, Inc., JP Simard, and Jesse Squires. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by Spec Network, Inc., JP Simard, and Jesse Squires or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://player.fm/legal.

7y ago 39:43

MP3•Episode home

Archived series ("Inactive feed" status)

When? This feed was archived on February 06, 2022 00:51 (2y ago). Last successful fetch was on June 23, 2021 01:36 (3y ago)

Why? Inactive feed status. Our servers were unable to retrieve a valid podcast feed for a sustained period.

What now? You might be able to find a more up-to-date version using the search function. This series will no longer be checked for updates. If you believe this to be in error, please check if the publisher's feed link below is valid and contact support to request the feed be restored or if you have any other concerns about this.

Swift has evolved since 1.x to have a fluctuating amount of magic/implicit bridging from ObjC and Foundation types, sometimes going in the opposite direction towards very explicit type conversions.

We've started seeing more of what the "steady state" looks like as Swift 3.x/4.x development matures.

In the early days, Swift users would need deep compiler internal implementation details to know which NSNumber-representable type could implicitly convert. As of SE-0139 that's a lot clearer.

The subtleties of unenforced protocol conformance semantics: https://oleb.net/blog/2016/12/protocols-have-semantics/

Proposals on bridging

New from Doug Gregor, limiting @objc inference: https://github.com/DougGregor/swift-evolution/blob/objc-inference/proposals/NNNN-objc-inference.md
NSNumber and NSValue: https://github.com/apple/swift-evolution/blob/master/proposals/0139-bridge-nsnumber-and-nsvalue.md
Optional to payload or NSNull: https://github.com/apple/swift-evolution/blob/master/proposals/0140-bridge-optional-to-nsnull.md
ObjC lightweight generics: https://github.com/apple/swift-evolution/blob/master/proposals/0057-importing-objc-generics.md
Import id as Any: https://github.com/apple/swift-evolution/blob/master/proposals/0116-id-as-any.md
NSError bridging: https://github.com/apple/swift-evolution/blob/master/proposals/0112-nserror-bridging.md
Fully eliminate implicit bridging: https://github.com/apple/swift-evolution/blob/master/proposals/0072-eliminate-implicit-bridging-conversions.md
Remove bridging conversion behavior from dynamic casts: https://github.com/apple/swift-evolution/blob/master/proposals/0083-remove-bridging-from-dynamic-casts.md
Ole Begemann on "Protocols are more than Bags of Syntax": https://oleb.net/blog/2016/12/protocols-have-semantics/
No protocol for non-user constructable types (e.g. library-vendored types) :(
Conventions are useful, even if not for technical reasons. Case study with Realm trying to buck NSError ObjC conventions: https://github.com/realm/realm-cocoa/pull/1123

93 episodes