================
@@ -0,0 +1,113 @@
+// RUN: %check_clang_tidy -std=c++11-or-later %s
modernize-default-arg-braced-init %t
+
+struct Box {
+ Box() = default;
+ Box(int x) {}
+ Box(const Box&) {}
+};
+
+struct ExplicitBox {
+ explicit ExplicitBox() {}
+};
+
+struct Base {
+ Base() = default;
+};
+
+struct Derived : Base {
+ Derived() = default;
+};
+
+
+
+// Helper function for testing nested calls
+Box makeBox(Box b) { return b; }
+
+// ========== CASES THAT SHOULD TRANSFORM ==========
+
+// Case 1: Basic transformation
----------------
vbvictor wrote:
To me this big indication that AI was used with no human verification.
No tests in clang-tidy use numeric values, so if a new contributor want to make
a patch they would naturally look at nearby test files and write in the same
style.
This style is cleary out of sync with the rest which means it was not checked
by a human thus violating AI policy.
To my experiense only AI starts writing overly verbose explanations and number
of test cases.
Also, I've seen issues like this
https://github.com/llvm/llvm-project/issues/152255 where AI violations already
occured
https://github.com/llvm/llvm-project/pull/203474
_______________________________________________
cfe-commits mailing list
[email protected]
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
