[swift-evolution] [Review] SE-0160: Limiting @objc inference

Slava Pestov spestov at apple.com
Thu Mar 23 03:46:10 CDT 2017

> On Mar 22, 2017, at 5:51 PM, Jordan Rose via swift-evolution <swift-evolution at swift.org> wrote:
> [Proposal: https://github.com/apple/swift-evolution/blob/master/proposals/0160-objc-inference.md]
> I'm definitely in favor of this. Apart from the various motivations discussed in the proposal, this also allows some changes that could improve incremental builds: the generated header ("MyApp-Swift.h") wouldn't need to be regenerated nearly as often with fewer methods exposed to Objective-C. (There's some nuance here that I don't need to go into right now, and there are alternate solutions to that problem, but it's nice that the common case will just put fewer declarations into the header and therefore it would change less often.)
> The migration aspect is a little scary. #selector's Objective-C equivalent is @selector, which is easy to search for, but #keyPath maps to plain old strings.

Are these strings usually literal strings that are passed in to some set of mostly-known selector names, or do people pass them around or even construct them dynamically?


> For those with Mac apps, properties might even be referenced in Interface Builder using Cocoa Bindings. But limiting the change to Swift 4 mode seems acceptable to me—at least it's a known change that people will be able to point to when things stop working.
> Jordan
> _______________________________________________
> swift-evolution mailing list
> swift-evolution at swift.org
> https://lists.swift.org/mailman/listinfo/swift-evolution

More information about the swift-evolution mailing list