Nathan Ridge

@esnosy As you may be aware, the LLVM project switched its code review system from Phabricator to Github PRs last year. Are you interested in picking up the patch at...

It may be somewhat instructive to look at CLion's approach to supporting modules, which first appeared in the latest 2022.3 release: https://blog.jetbrains.com/clion/2022/11/clion-2022-3-released/#cpp_modules It's somewhat light on details but this part...

> And what is good as the first step? I think it may be good if: > > * We can collect the potential module files by clang-scan-deps in the...

> (1) When the clangd server initializes, will `BackgroundIndex::changedFilesTask` get called? Yes, when the compilation database is loaded, it calls [this function](https://searchfox.org/llvm/rev/50dfc9e35d72bf783ebc514ad1e48bd4d0767c5d/clang-tools-extra/clangd/index/Background.cpp#104) with all of the entries in the database,...

> I feel like the there is only one TUScheduler in one project (is this true?) I believe so. > So the BMIs won't be rebuilt every time we opened...

> > The indexer also triggers AST builds (for every file in the project that isn't already indexed), that happens around [here](https://searchfox.org/llvm/rev/50dfc9e35d72bf783ebc514ad1e48bd4d0767c5d/clang-tools-extra/clangd/index/Background.cpp#281). That AST build will encounter imports, so I...

> > Is there an opportunity to reuse this persisted BMI cache between the indexer and the preambles of open files? > > The "lite mode" ASTs (skip-function-bodies etc) may...

> Is there any update on this or a workaround? It makes the whole thing unusable for me. Perhaps you could post some [clangd logs](https://clangd.llvm.org/troubleshooting#gathering-logs) so we can verify you're...

@Kairo-Dai I can't tell from your comments what issue you're running into. Can you please provide [clangd logs](https://clangd.llvm.org/troubleshooting#gathering-logs)? I would also recommend filing a new issue. We can always dupe...

> Alternatively... maybe instead of rolling our own builds, we could just arrange for the LLVM project buildbots that build the LLVM packages for various platforms, to also build clangd-only...