__fin__
Studio 8502 
I would like someone who knows more than me to explain, in technical terms, what exactly the open source Swift compiler is missing, that Apple’s shipped version in Xcode has, that makes the Objective-C bridge not work. I know the Swift project doesn’t want to support it, I know all the social and political reasons, I am asking strictly about the technological reasons. It can’t be as simple as a compile time option, there has to be something missing at the low level, or someone would have released a fork of the compiler with it enabled by now.
Stijn Willems@mos_8502 could you clarify what is missing. You can make a swift package with an objective c only target that bridges just fine to objective c. But I guess you already know that and your question is not that?
@Doozmen Go build Swift on Linux, and try using it to talk to Objective-C. Then you'll see what I mean.
Ted C. Howard@mos_8502 there’s some details in this thread: https://forums.swift.org/t/state-of-gnustep-interop/50950/18
State of gnustep interop
Hey everyone. This is something I am very interested in. I am the lead developer on the GNUstep project. I and others have been diligently working to make GNUstep as close to 10.14 (Catalina) as possible. We are not that far away from this at the moment. I have been very busy, as you can imagine. Swift integration is something I would very much like to see happen. Preferably, it would be so that code originally built for macOS using Swift could be seamlessly compiled on systems which...
@tedchoward This here? This makes me want to hit something.
If it's as simple as a compile-time flag and pointing it to an Objective-C runtime, then someone should be maintaining a fork that's just "the latest official Swift release for non-Apple, but with the ObjC stuff turned back on". Which is why I assumed there was some technical barrier.