enabled and mitigated readability-const-return-type clang-tidy warnings#5644
Conversation
0956a56 to
6586d00
Compare
6586d00 to
9b5a688
Compare
|
Still need to file upstream tickets about the false positive and lacking context: |
| void ProjectFileDialog::setSuppressions(const QList<Suppressions::Suppression> &suppressions) | ||
| { | ||
| mUI->mListSuppressions->clear(); | ||
| // NOLINTNEXTLINE(readability-const-return-type) - neeeds to be a copy since it might be a reference to mSuppressions |
There was a problem hiding this comment.
Is this really related?
There was a problem hiding this comment.
There is no return type on that line, so what does clang-tidy warn about?
There was a problem hiding this comment.
Good point. Maybe yet another false positive in this check. Although it is a valid warning and possibly even a false negative on our side.
There was a problem hiding this comment.
Sounds like the NOLINT should be for performance-unnecessary-copy-initialization?
There was a problem hiding this comment.
If it would report that warning and we would not suppress it correctly the CI would fail.
There was a problem hiding this comment.
Yeah, but unmatched NOLINTs don't seem to cause a warning: llvm/llvm-project#69674
There was a problem hiding this comment.
Yeah - this is unrelated. Will revert.
9b5a688 to
6bfcc81
Compare
|
I filed llvm/llvm-project#73270 about the missing context. |
No description provided.