ArcsinX wrote: > In the separate tool scenario: > ... > * The generated index is transformed per user (potentially via `dexp`), > specifying `/generation/location=/user/location` in some
In separate tool scenario transformation can be done on the user side. I.e. users get the index and transform paths > How expensive is retranslating a massive index N times versus lazily > translating for the files a user opens? With current PR paths transformation happens every time user opens the project and this transformation applies to the whole project (and if index needs some updates, we need additional transformations from local paths to remote paths to keep the index with remote paths inside). So, if every user opens a re-opens the project in average M times a day, we will get N*M paths transformations for the whole project, but not for a single files. With a separate tool, user needs to apply paths mappings only once and after that he will work with the index using his local paths. https://github.com/llvm/llvm-project/pull/180285 _______________________________________________ cfe-commits mailing list [email protected] https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
