[cfe-dev] Avoid generating replacement text for code expanded from macros with clang-tidy

[Jonathan Coe]

I'm finishing up a clang-tidy check for uninitialized fields.

How can I prevent replacement text being generated when the class or
constructor is part of a macro expansion?

I'm getting a few silly replacement suggestions when running the check over
llvm source.

thanks,

Jon
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/cfe-dev/attachments/20150618/4f8a1ae9/attachment.html>