This fixes bug https://llvm.org/bugs/show_bug.cgi?id=26747
Details
- Reviewers
JVApen aaron.ballman alexfh - Commits
- rGb6947a58473f: [clang-tidy] ProTypeMemberInitCheck - check that field decls do not have in…
rCTE268352: [clang-tidy] ProTypeMemberInitCheck - check that field decls do not have in…
rL268352: [clang-tidy] ProTypeMemberInitCheck - check that field decls do not have in…
Diff Detail
Event Timeline
I'm not sure if I'm the right person to do reviews, as I'm mostly a user of the tool and have not yet done any developments or bug fixes to it.
However, from what I know from coding, this looks good to me.
test/clang-tidy/cppcoreguidelines-pro-type-member-init.cpp | ||
---|---|---|
94 | Why is this checking a fix? I thought that point was that this should not generate any diagnostic (and hence, no fix is required)? |
test/clang-tidy/cppcoreguidelines-pro-type-member-init.cpp | ||
---|---|---|
94 | If I understood Alex correctly, CHECK-FIXES is needed to check for the absence of a change made by ClangTidy. But I agree it seems unlikely to have a change without a warning message which will trigger a test failure at any rate. |
Missed this patch somehow: it was in a wrong part of my dashboard =\
LG. Thanks for the fix.
test/clang-tidy/cppcoreguidelines-pro-type-member-init.cpp | ||
---|---|---|
94 | I usually ask people to add CHECK-FIXES in case when there is a warning that could change some code, but shouldn't. When there's no warning that is likely to touch some code, there's no need for a CHECK-FIXES to verify this. |
I should free up again soon, just caught the flu though. Maybe next week?
Feel free to commit before then.
Why is this checking a fix? I thought that point was that this should not generate any diagnostic (and hence, no fix is required)?