aboutsummaryrefslogtreecommitdiffstats
path: root/src/checks/level1/README-connect-3arg-lambda.md
diff options
context:
space:
mode:
Diffstat (limited to 'src/checks/level1/README-connect-3arg-lambda.md')
-rw-r--r--src/checks/level1/README-connect-3arg-lambda.md21
1 files changed, 0 insertions, 21 deletions
diff --git a/src/checks/level1/README-connect-3arg-lambda.md b/src/checks/level1/README-connect-3arg-lambda.md
deleted file mode 100644
index 1ec7c146..00000000
--- a/src/checks/level1/README-connect-3arg-lambda.md
+++ /dev/null
@@ -1,21 +0,0 @@
-# connect-3arg-lambda
-
-Warns when using the 3-arg `QObject::connect` that takes a lambda.
-The recommendation is to use the 4-arg overload, which takes a context object
-so that the lambda isn't executed when the context object is deleted.
-
-It's very common to use lambdas to connect signals to slots with different number
-of arguments. This can result in a crash if the signal is emitted after the receiver
-is deleted.
-
-Another reason for using a context-object is so you explicitly think about in
-which thread you want the slot to run in. Note that with a context-object the
-connection will be of type `Qt::AutoConnection` instead of `Qt::DirectConnection`,
-which you can control if needed, via the 5th (optional) argument.
-
-
-In order to reduce false-positives, it will only warn if the lambda body dereferences
-at least one QObject (other than the sender).
-
-It's very hard to not have any false-positives. If you find any you probably can just
-pass the sender again, as 3rd parameter.