sammccall added a comment. Good/bad news on timing here...
I'd like to introduce a config system (user config file, but also eventually in-project `.clangd` files, extensible over LSP etc). It'll provide a generic way to apply different config to different files. And it'll be YAML files on disk so it'll be simpler to supply such structured config (and still possible to provide config on the command-line). I was literally going to send the design doc out today: http://tinyurl.com/clangd-config This would replace most of our separate "user-pref"-like command-line flags (deprecate and maybe eventually remove). As such I'm not sure introducing another one for fairly deep config is a good idea. On the other hand, the scope for the config would be deliberately small for the LLVM 11 release, so we'd probably want to add clang-tidy config after the branch in a month, delaying it for one release cycle. How pressing is this? Repository: rG LLVM Github Monorepo CHANGES SINCE LAST ACTION https://reviews.llvm.org/D81975/new/ https://reviews.llvm.org/D81975 _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
