Integration with Xcode would be straightforward but it’s been Android Studio I’ve most experience with. For that it was just a case of adapting a gradle plugin to add a rebuild phase. If you can’t automate it running a generator when you change the surface of your api is not a big overhead.
Supporting playgrounds would involve being able to import a user module to publish the api and link with python. Is that possible? John > On 11 Nov 2017, at 18:20, Chris Lattner <[email protected]> wrote: > > > >> On Nov 11, 2017, at 9:53 AM, Joe Groff via swift-evolution >> <[email protected] <mailto:[email protected]>> wrote: >> >> >> >> On Nov 11, 2017, at 9:44 AM, John Holdsworth <[email protected] >> <mailto:[email protected]>> wrote: >> >>> Isn’t there a third way? I wrote a bridge between Swift and Java without >>> having to >>> change the compiler at all by using a code generator to generate bridging >>> Swift >>> rather than having a Java importer. >> >> Good point. For unidirectional importing without deep support for overriding >> or runtime integration like what we do with ObjC, which AIUI is the extent >> of Chris's ambition with Python interfacing here, a code generator can get >> the job done without requiring deep compiler integration, though at the >> expense of needing an added tool in your build process. Have you looked at >> all into making SwiftJava integrate with the package manager or with Xcode >> yet? How's that experience? > > Also, what is the playground experience like? > > -Chris > >
_______________________________________________ swift-evolution mailing list [email protected] https://lists.swift.org/mailman/listinfo/swift-evolution
