t-a-james wrote: > > The check name is a bit too vague/general, I would call it > > `bugprone-derived-method-shadowing-base-method` or similar. You can easily > > apply the renaming with the `rename_check.py`. But let's wait until there's > > some consensus on this. > > Agree, initially I was thinking about `bugprone-method-shadowing`: it's > concise and not overwhelming IMO
Funnily enough, `bugprone-derived-method-shadowing-base-method` is very close to what this is called in our downstream project. Just pushed something that re-names the check. https://github.com/llvm/llvm-project/pull/154746 _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
