You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Xcode 7.3b5 with swift-DEVELOPMENT-SNAPSHOT-2016-03-01-a
Additional Detail from JIRA
Votes
0
Component/s
Labels
Bug
Assignee
None
Priority
Medium
md5: 7e5f065cdfa911edc13afa2e01139a07
duplicates:
SR-492 Protocol extenstion methods aren't exposed to Objective-C
Issue Description:
If you have an @objc protocol, provide a default implementation of methods in it via an extension, and then conform to that protocol in an @objc class, the compiler emits errors about the methods being not-@objc.
It seems like since the extension is on an @objc protocol, the methods defined in the extension should be @objc and the compiler should clone them into the conforming class when the conformance is declared (last line in the sample).
Attachment: Download
Environment
Xcode 7.3b5 with swift-DEVELOPMENT-SNAPSHOT-2016-03-01-a
Additional Detail from JIRA
md5: 7e5f065cdfa911edc13afa2e01139a07
duplicates:
Issue Description:
If you have an @objc protocol, provide a default implementation of methods in it via an extension, and then conform to that protocol in an @objc class, the compiler emits errors about the methods being not-@objc.
It seems like since the extension is on an @objc protocol, the methods defined in the extension should be @objc and the compiler should clone them into the conforming class when the conformance is declared (last line in the sample).
This seems possibly related to https://bugs.swift.org/browse/SR-492 but in my case the protocol and class involved are already marked as @objc.
The text was updated successfully, but these errors were encountered: