sammccall added a comment. > indicating how I would disentangle that code if I owned it. Hopefully that > comment clarifies my position somewhat.
So your position on how to best write that code is interesting (I disagree, but I think there are probably types of projects where your priorities are the right ones. Maybe clang itself is one of them!) But what would be really useful is to clarify your position on whether the warning in clang is delivering value. E.g. that you do want it enabled for clang, so we should rather turn this off at the clangd level. Repository: rG LLVM Github Monorepo CHANGES SINCE LAST ACTION https://reviews.llvm.org/D82617/new/ https://reviews.llvm.org/D82617 _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
