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
Version 9.4.1 (9F2000)
Apple Swift version 4.1.2 (swiftlang-902.0.54 clang-902.0.39.2)
Target: x86_64-apple-darwin17.7.0
Additional Detail from JIRA
Votes
0
Component/s
Compiler
Labels
Bug
Assignee
None
Priority
Medium
md5: 069d4fcfef4032456a654b908006d25d
duplicates:
SR-4827 Incorrect result resolving type for Obj-C block
Issue Description:
When defining a protocol in Swift which is renamed for Objective-C, the protocol makes any method that uses this renamed protocol in Objective-C unavailable for Swift.
Example for the protocol:
When importing this class in bridging header and some Swift code tries to access this method, the compiler fails with the message "Argument passed to call that takes no arguments":
let _ =SomeClass(someProtocol:nil)
Find attached a project which demonstrates the problem.
When the protocol is not renamed through the @objc annotation, the initializer can be called without an error.
The text was updated successfully, but these errors were encountered:
Attachment: Download
Environment
Version 9.4.1 (9F2000)
Apple Swift version 4.1.2 (swiftlang-902.0.54 clang-902.0.39.2)
Target: x86_64-apple-darwin17.7.0
Additional Detail from JIRA
md5: 069d4fcfef4032456a654b908006d25d
duplicates:
Issue Description:
When defining a protocol in Swift which is renamed for Objective-C, the protocol makes any method that uses this renamed protocol in Objective-C unavailable for Swift.
Example for the protocol:
Then use this protocol from Objective-C:
When importing this class in bridging header and some Swift code tries to access this method, the compiler fails with the message "Argument passed to call that takes no arguments":
Find attached a project which demonstrates the problem.
When the protocol is not renamed through the
@objc
annotation, the initializer can be called without an error.The text was updated successfully, but these errors were encountered: