sammccall added a comment. This is definitely an interface that makes sense for the purpose you describe (profiling index performance) but I'm less convinced it makes sense for clangd's *primary* use cases.
For example, our default policy gives different answers for code in different paths, which has some desirable properties (e.g. once you stop working on a project, its index files can be removed in an obvious way without disturbing other projects). A mechanism that allows customization but has its own limitations can add confusion without actually solving many more people's problems. And generally we're trying to phase out use of global command line flags in favor of config files while carefully limiting the amount of options users need to understand. Given that there are some workarounds available (compile-commands dir, making the `.cache` directory a symlink, maybe even using `clangd-indexer` instead depending on your purpose) I think we probably shouldn't add this option, or should at least defer it until we have more info on what kind of customization people need while using clangd together with an editor. Repository: rG LLVM Github Monorepo CHANGES SINCE LAST ACTION https://reviews.llvm.org/D103377/new/ https://reviews.llvm.org/D103377 _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
