[SR-7130] ObjC protocol objects are not emitted #49678
Assignees
Comments
|
@swift-ci create |
|
Comment by Florent Vilmart (JIRA) @belkadan if you guys have any pointers, I would very well try to understand and fix this issue! |
|
I believe that #15338 addresses this, but it needs more testing. graydon (JIRA User) did most of the investigation here; I just knew which body to dig up. |
|
Comment by Florent Vilmart (JIRA) @DougGregor if you can let me know when it lands in a toolchain snapshot, I'll re-run my tests to make sure the fix is ok? |
|
Comment by Graydon Hoare (JIRA) flovilmart (JIRA User) I have the testcase here and am currently testing it against a trunk compiler with Doug's fix. Will let you know shortly if it works here (and thus whether to bother with a snapshot yet). |
|
Comment by Florent Vilmart (JIRA) Awesome |
This issue was closed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Environment
MacOS High Sierra 10.13.3 (17D102)
Xcode Version 9.2 (9C40b)
Swift 4.0
j2objc 2.0.5, with latest JRE (https://github.com/google/j2objc)
Additional Detail from JIRA
md5: 96e75817b9a0ee2e3ff7689a8b1ee8d7
Issue Description:
While using j2objc, the google backed java to objective-c translation library we encounter this bug when checking for protocol conformances from a swift codebase.
An objective-c codebase is not affected by the issue.
The issue is tracked here, and seems to originate with the release of Swift 3.0 google/j2objc#889
We put together a demo project https://github.com/flovilmart/TestingObjCProtocolIssue with all required dependencies for easy 'testing'.
This has also been briefly discussed on twitter (https://twitter.com/jckarter/status/971104252432039936)
At this time, I can't pinpoint nor provide more details, but it seems that in particular scenarios, the protcol objects are not properly emitted.
The text was updated successfully, but these errors were encountered: