Marc Rousavy comments

Results 1826 comments of


                                            Marc Rousavy

The autogenerated `-Swift.h` header generates broken code when a class in a module inherits from a class inside another module

I did try this in a CocoaPods Xcode project, and the `-Swift.h` header from one module is just not available in another module. And if I manually add it (via...

The autogenerated `-Swift.h` header generates broken code when a class in a module inherits from a class inside another module

Hey @Xazax-hun - is there anything you need from my end to help troubleshoot this? I can try to generate a test case for this behaviour to see if this...

The autogenerated `-Swift.h` header generates broken code when a class in a module inherits from a class inside another module

Thanks & no stress! I'll try to play around with frameworks. I think the main problem is that I cannot import `SecondPod`'s generated `SecondPod-Swift.h` header in my `FirstPod` (before I...

The autogenerated `-Swift.h` header generates broken code when a class in a module inherits from a class inside another module

JFYI, even after I managed to import `SecondPod-Swift.h` before `FirstPod-Swift.h`, it fails to build because the Swift compiler defines `swift::isUsableInGenericContext` for the same type twice: Which makes sense, because both...

The autogenerated `-Swift.h` header generates broken code when a class in a module inherits from a class inside another module

I spent ~2 more days on this to try and work around the issue. I think one way to solve this is if the generated `-Swift.h` header doesn't to everything...

The autogenerated `-Swift.h` header generates broken code when a class in a module inherits from a class inside another module

After adjusting the test examples a bit, I noticed that it doesn't have anything to do with inheritance, it also applies to just any externally used Swift type. Not just...