torarnv wrote: A downside of this approach is that it isn't backwards compatible, so any `clang` that doesn't know about this new syntax will fail AFAICT. Which sort of defeats the point a bit, since the goal was to make `swift` pick up swift-specific-module files while leaving all other consumers unaffected đ
An alternative that might be easier would be to add an option similar to `-fno-implicit-module-maps`, but for specific modules, e.g. `-fno-implicit-module=module-id` or `-fno-implicit-module-file=<file>`. Then the Qt build system could propagate `-fno-implicit-module=QtCore` for any C++ consumers via qmake/CMake, while `swift` consumers would pick up the module file as usual. Thoughts? https://github.com/llvm/llvm-project/pull/207515 _______________________________________________ cfe-commits mailing list [email protected] https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
