MyDeveloperDay added a comment. I am not opposed to this idea, I actually think this has some mileage based on a use case I've encountered:
our team tends to use windows builds of clang-format from (https://llvm.org/builds/) because its easy to distribute the installer, this is ok but sometimes these snapshot builds can lag new features by 1-2 months This can make introducing a new configuration option a problem because it requires us to have to get everyone upgraded before we can change the checked in .clang-format at the top of the tree. If everyone isn't upgraded they start getting complaints about unknown configurations. Its not 100% obvious if those styles are being ignored, if no formatting at all is being done or if when clang-format is embedded inside Visual Studio or VIM what exactly is happening. I see this feature would allow those on the bleeding edge to use an alternate .clang-format file (even if that was also in the root /.clang-format-next Repository: rC Clang CHANGES SINCE LAST ACTION https://reviews.llvm.org/D50147/new/ https://reviews.llvm.org/D50147 _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
