Hi everyone,
New AppCode 2017.3 EAP (build 173.3531.19) is available for download on our site. This build brings the following major improvements for resolve in Swift and mixed Objective-C/Swift code:
- Correct resolve for initializers of classes written in Objective-C (OC-13087) in Swift code.
- False “Parameter type mismatch” inspection in the mixed Objective-C/Swift code (OC-14076). This issue affected lots of general cases in the resolution and completion also causing other false inspections in the Objective-C code.
- Wrong method resolve when a variable in the code has the same name (OC-11986).
- Fix for exception that led to resolve problems in mixed Swift/Objective-C code (OC-16248)
We encourage everyone who experienced similar issues before to try this build and share feedback with us.
The full release notes are available here.
Your AppCode team
JetBrains
The Drive to Develop
Great news! Here is a screenshot of the same file with mixed code before the update to the new EAP and after: http://goloskok.com/u/interop-F8gxdpgaVi.png
Just upgraded so may have more details later but quickly checking – there are still a couple of issues left in the sample project I’ve made for you guys some time ago: https://github.com/alexandre-g/InteroperabilityTestAppcode
Namely, ‘Incompatible pointer types’ and ‘Cannot resolve method’
Thanks for the project. First issue (‘cannot resolve method’) is caused by https://youtrack.jetbrains.com/issue/OC-15031. Second one (‘incompatible pointer types’) is happening due to incorrect translation of closures (https://youtrack.jetbrains.com/issue/OC-16047). Please vote for those tickets.
There seems to be a regression with these false warnings:
Parameter type ‘UITableView *’ of overridden method doesn’t match the parameter type (UITableView *) of base method
http://www.goloskok.com/u/image-cuQBkSaBc6.png
http://www.goloskok.com/u/image-W8sdJV0zbn.png
Alex, thanks for the quick report. I’ve filed https://youtrack.jetbrains.com/issue/OC-16266. We’ll try to fix it in upcoming EAP(s).