nridge added a comment. In D124909#3501896 <https://reviews.llvm.org/D124909#3501896>, @sammccall wrote:
> I think first steps are pretty high level, to understand: > > - what the goals are (e.g. performance, easier integration with build system, > work with modules syntax features, ...) I'll start by suggesting (what seems to me is) a modest goal: a C++ project that wishes to use / start using Modules should be able to do so without breaking their developers' ability to use clangd to work on the project. That is, clangd should be able to understand Modular code //somehow//; performance may not be optimal (e.g. clangd may have to parse modular headers from source rather than consuming a compiled module artifact), and it may require some extra configuration (e.g. developers may have to add things to `.clangd` to get the setup to work) -- those are areas where we can consider improvements (e.g. using a compiled module artifact if one is available) in the future. Repository: rG LLVM Github Monorepo CHANGES SINCE LAST ACTION https://reviews.llvm.org/D124909/new/ https://reviews.llvm.org/D124909 _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
