Lambda expression

Reports any C++ lambda expression, regardless of its capture list.

A lambda’s captured state is invisible at its call site and, for a reference capture, is only as long-lived as whatever it refers to - a lambda stored and invoked after its captured references go out of scope is a dangling-reference use-after-free. Lambdas also make it easy to grow deeply nested, hard-to-name, hard-to-unit-test blocks of logic inline. Some safety-critical and embedded coding standards forbid lambdas outright in favor of named, independently testable functions with an explicit parameter list.

The following code illustrates the pattern detected by this rule:

Extract the lambda body into a named function (or function object) that takes its former captures as explicit parameters. If a callback interface is genuinely required, pass a function pointer or a named functor instead of an inline lambda.

This detector does not need any configuration.