Basic usage of ObjectiveCBridgeable protocol on Linux #303
Conversation
|
Relies on swift pull request swiftlang/swift#1994 which makes the protocol available. |
|
Thanks Dave. Let's hold on to this and make sure the other PR goes through. |
|
I guess the other followup part is to test via removing the calls to |
|
Agreed. I can start going through the tests. I can structure either as a separate pull request or as an addendum to this one. Either is fine with me. |
|
I think it may be best to have them separate just in case we get compiler crashes from the as conversion |
|
Test suite update in #310 |
Add extensions to Bridgeable types to define their conformance to the _ObjectiveCBridgeable protocol in terms of the existing bridging support. Since the compiler understands the semantics of _ObjectiveCBridgeable this allows 'as' conversions to be performed to/from various NS types on platforms without ObjectiveC.
|
rebased to master as of 4/25; updated for Swift change for first argument labels; squashed to single commit. |
|
I'm going to follow up on this with some swift compiler engineers and get back to you on it. The recent back and forth with implicit bridging going away has confused things... |
|
ok, thanks Tony. I'm happy with any outcome. If we need this, I will rebase it. If we don't need it after all, no problem...I learned a few things doing it. |
|
not needed; closing. |
3 participants
Add extensions to Bridgeable types to define
their conformance to the ObjectiveCBridgeable
protocol in terms of the existing bridging
support. Since the compiler understands the
semantics of ObjectiveCBridgeable this allows
'as' conversions to be performed to/from various
NS types on platforms without ObjectiveC.