I don't see anything wrong with having a bootstrap process that begins with cross-compilation. After all, that's probably how your platform got its first C compiler, too.
I believe that Chris Lattner the original author of LLVM also started Swift and is (or was) working at Apple on compilers.
And Chris Lattner has worked at Google for a while now.
I remember hacking the original C++ version of this, trying to pass wasm target compilation flags back to the llvm just for fun.
What more can you get from this.. the ability to fiddle with the build process from Swift API? For consumers like package managers?
I guess it needs a little bit more of clarification, of what can be done with it.. i guess, a introduction to the API behind it would help, giving the target audience for this sort of thing.
I've changed a GN(chrome ninja build generator) to build Swift, and unlike C/C++ code where you compile each file, i had to create a different scheme to compile all source files into the the final object module file.
Wonder if i can call this instead of swiftc directly and if it would help somewhere.
Yeah, SwiftPM being one obvious candidate of course.