<div dir="ltr">Awesome, thanks! I'll give it a try when I find some time :) <div><br></div><div>/Carlos</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Oct 5, 2021 at 4:12 PM Aaron Ballman <<a href="mailto:aaron@aaronballman.com">aaron@aaronballman.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On Tue, Oct 5, 2021 at 9:42 AM Carlos Galvez via cfe-dev<br>
<<a href="mailto:cfe-dev@lists.llvm.org" target="_blank">cfe-dev@lists.llvm.org</a>> wrote:<br>
><br>
> Hi,<br>
><br>
> Currently it's annoying or sometimes impossible (due to line length limit) to accurately inline-suppress clang-tidy warnings. For example:<br>
><br>
> // NOLINT(cppcoreguidelines-non-private-member-variables-in-classes,misc-non-private-member-variables-in-classes)<br>
><br>
> This is not an uncommon case of someone enabling both a "coding guideline" module and "best practices" module.<br>
><br>
> The solution turns into a very bad practice, which is disabling all warnings, potentially hiding additional bugs:<br>
><br>
> // NOLINT<br>
><br>
> Proposal: support globbing for NOLINT expressions, with the same format/semantics as when enabling/disabling checks:<br>
><br>
> // NOLINT(*-non-private-member-variables-in-classes)<br>
><br>
> What do you think?<br>
<br>
I think it's a good idea -- we already support some of the globbing<br>
functionality today (<a href="https://godbolt.org/z/jTsahYnbM" rel="noreferrer" target="_blank">https://godbolt.org/z/jTsahYnbM</a>), so this<br>
proposes to extend it in a useful way.<br>
<br>
~Aaron<br>
<br>
><br>
> /Carlos<br>
> _______________________________________________<br>
> cfe-dev mailing list<br>
> <a href="mailto:cfe-dev@lists.llvm.org" target="_blank">cfe-dev@lists.llvm.org</a><br>
> <a href="https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev" rel="noreferrer" target="_blank">https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev</a><br>
</blockquote></div>