[PATCH] D153114: [clangd] [C++20] [Modules] Support C++20 modules for clangd

[Nathan Ridge via Phabricator via cfe-commits]

nridge added a comment.

> The major problem I see now is that we can't handle third party modules. Third party modules refer to the modules whose source codes are not in current project. The users are still able to see the hint from clangd if the BMI of the third party modules are built ahead of time. I think this is true for a lot use cases. But this breaks our goal to not be locked by the same version compiler.
>
> I think we can only solve the issue after SG15 solves it. I know SG15 is discussing how to let the modules communicate across libraries boundary. And it is not wise to invent wheels agains SG15. So let's wait for that.

For context, SG15 is the ISO C++ standards committee's Tooling Study Group. One proposal being looked at that may be relevant here is P2581 - Specifying the Interoperability of Built
Module Interface Files <https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2022/p2581r2.pdf>.


CHANGES SINCE LAST ACTION
  https://reviews.llvm.org/D153114/new/

https://reviews.llvm.org/D153114