[swift-users] Discrepancy between sharing internal Swift symbols with Obj-C when in an app vs a framework target

Kevin Lundberg kevin at klundberg.com
Sat Jun 4 18:45:57 CDT 2016

Its not just methods, but types themselves. Even if this was a solution
I'd still have to manually fix all build issues by prepending dynamic to
everything that needs it :(

On 6/4/2016 2:56 PM, Austin Zheng wrote:
> This is probably a solution to a different issue, but what happens if
> you declare your "should be visible from Objective-C" swift methods as
> 'dynamic'?
> Austin
>> On Jun 4, 2016, at 11:55 AM, Jens Alfke via swift-users
>> <swift-users at swift.org <mailto:swift-users at swift.org>> wrote:
>>> On Jun 4, 2016, at 11:29 AM, Kevin Lundberg via swift-users
>>> <swift-users at swift.org <mailto:swift-users at swift.org>> wrote:
>>> However objc code inside the same framework as the swift code in
>>> question should ideally be able to see internal swift symbols as
>>> well, as they are within the same module.
>> I agree; I didn’t realize that was your situation. I haven’t tried
>> doing this myself. It sounds like a bug.
>> —Jens
>> _______________________________________________
>> swift-users mailing list
>> swift-users at swift.org <mailto:swift-users at swift.org>
>> https://lists.swift.org/mailman/listinfo/swift-users

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-users/attachments/20160604/a634b99e/attachment.html>

More information about the swift-users mailing list