[cfe-dev] [clang-tidy] Dealing with check names
Piotr Padlewski via cfe-dev
cfe-dev at lists.llvm.org
Mon Dec 12 10:52:26 PST 2016
2016-12-12 18:29 GMT+01:00 Richard via cfe-dev <cfe-dev at lists.llvm.org>:
>
> [Please reply *only* to the list and do not include my email directly
> in the To: or Cc: of your reply; otherwise I will not see your reply.
> Thanks.]
>
> In article <CAEhrgAPqzCPZhtJ7qbgk+V-Vc_T-wSBsgPWHg74dj4QSrg4SZQ at mail.
> gmail.com>,
> Piotr Padlewski via cfe-dev <cfe-dev at lists.llvm.org> writes:
>
> > This sounds also good. I was thinking that it would be nice if clang-tidy
> > itself could warn about old name and dump config, but problem here is
> > when user have configuration "misc-*" and we moved one check from misc to
> > other group. We should probably dump clang-tidy version in the config to
> > know how old is config.
>
> I believe clang-tidy already has a mechanism for saying "this check is
> an alias of this other check", so you can migrate the checks to a new
> organization and keep the old names as aliases for the new names.
>
> I know about the aliases.
> I don't know if it emits any kind of diagnostic that you are using an
> old alias. We could introduce a way of deprecating a check name and
> emit if you use the deprecated name.
>
The problem that I mentioned, if we move one check and someone is enabling
it with asterisk ("misc-*")
then having the todays config we would not know if the user meant to use
old check or not.
> --
> "The Direct3D Graphics Pipeline" free book <http://tinyurl.com/d3d-
> pipeline>
> The Terminals Wiki <http://terminals-wiki.org>
> The Computer Graphics Museum <http://ComputerGraphicsMuseum.org>
> Legalize Adulthood! (my blog) <http://LegalizeAdulthood.wordpress.com>
> _______________________________________________
> cfe-dev mailing list
> cfe-dev at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/cfe-dev/attachments/20161212/e7ecade9/attachment.html>
More information about the cfe-dev
mailing list