Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clang-tidy: Allow wildcards in bugprone-reserved-identifier.AllowedIdentifiers #59119

Closed
ke-kx opened this issue Nov 21, 2022 · 2 comments
Closed
Labels
clang-tidy enhancement Improving things as opposed to bug fixing, e.g. new or missing feature question A question, not bug report. Check out https://llvm.org/docs/GettingInvolved.html instead!

Comments

@ke-kx
Copy link

ke-kx commented Nov 21, 2022

Currently it doesn't seem to be possible to use wildecards in the bugprone-reserved-identifier.AllowedIdentifiers option for the bugprone-reserved-identifier check.

This would be useful for avoiding false positives on functions prefixed with __wrap which are often used to mock functions in unit tests.

See also:

@EugeneZelenko EugeneZelenko added enhancement Improving things as opposed to bug fixing, e.g. new or missing feature clang-tidy and removed new issue labels Nov 21, 2022
@llvmbot
Copy link
Collaborator

llvmbot commented Nov 21, 2022

@llvm/issue-subscribers-clang-tidy

@carlosgalvezp
Copy link
Contributor

To clarify - are you getting these warnings on the mocking framework itself (third-party code), not on your own source code? To solve that problem, make sure you include the third-party code as system headers, then clang-tidy won't throw warnings in there.

@EugeneZelenko EugeneZelenko added the question A question, not bug report. Check out https://llvm.org/docs/GettingInvolved.html instead! label Jul 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
clang-tidy enhancement Improving things as opposed to bug fixing, e.g. new or missing feature question A question, not bug report. Check out https://llvm.org/docs/GettingInvolved.html instead!
Projects
None yet
Development

No branches or pull requests

4 participants