[swift-evolution] [pitch] make @nonobjc the default
cocoadev at charlessoft.com
Wed Oct 19 13:28:37 CDT 2016
> On Oct 19, 2016, at 1:26 PM, Joe Groff via swift-evolution <swift-evolution at swift.org> wrote:
> If we move to this on-demand model for @objc-ness, then it seems to me we can potentially get away from @objc having to be a thing. The constraints on being representable in ObjC can still be enforced by the operation that demands an ObjC method, whether that be an attribute on the declaration itself or an operation that references the declaration.
Unless you’re making a library or a plugin or something that can’t completely know whether it’s being accessed by Objective-C clients.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the swift-evolution