doc: Clarify why performance-move-const-arg.CheckTriviallyCopyableMove=false
What the developer wrote
Authored by MarcoFalke
doc: Clarify why performance-move-const-arg.CheckTriviallyCopyableMove=false
What changed, and why it matters
This commit only adds a comment to a configuration file explaining why a clang-tidy linting option is turned off. It does not change any executable code, build settings, or security behavior. It is purely documentation.
No action needed; this is a non-functional documentation-only change.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff modifies src/.clang-tidy, changing the line ‘value: false’ to ‘value: false # Disabled, to allow the bugprone-use-after-move rule on trivially copyable types, to catch logic bugs’. No functional change is introduced; the comment clarifies the rationale for keeping performance-move-const-arg.CheckTriviallyCopyableMove disabled so that bugprone-use-after-move remains active for trivially copyable types.
Changed components
src/.clang-tidyInspect captured patch +1 / −1
diff --git a/src/.clang-tidy b/src/.clang-tidy
index cd42491a..9bdcc03f 100644
--- a/src/.clang-tidy
+++ b/src/.clang-tidy
@@ -37,7 +37,7 @@ CheckOptions:
- key: modernize-deprecated-headers.CheckHeaderFile
value: false
- key: performance-move-const-arg.CheckTriviallyCopyableMove
- value: false
+ value: false # Disabled, to allow the bugprone-use-after-move rule on trivially copyable types, to catch logic bugs
- key: bugprone-unhandled-self-assignment.WarnOnlyIfThisHasSuspiciousField
value: false
- key: bugprone-unused-return-value.CheckedReturnTypes
Why this scored 15/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.