StarMirror/CppCoreGuidelines
1
0
Fork 0
mirror of https://github.com/isocpp/CppCoreGuidelines.git synced 2024-03-22 13:30:58 +08:00
Code Issues Projects Releases Wiki Activity

Corrected F.54 example

Browse Source
This commit is contained in:
hsutter 2016-01-12 12:02:59 -08:00
parent 7ae6ad4eb7
commit b97f67cd60
1 changed files with 3 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
CppCoreGuidelines.md
View File

@ -3071,6 +3071,8 @@ It's confusing. Writing `[=]` in a member function appears to capture by value,
// ...
auto lambda = [=]{ use(i,x); }; // BAD: "looks like" copy/value capture
// notes: [&] has identical semantics and copies the this pointer under the current rules
// [=,this] and [&,this] are identical in this case, and still confusing in general
x = 42;
lambda(); // calls use(42);
x = 43;
@ -3078,13 +3080,7 @@ It's confusing. Writing `[=]` in a member function appears to capture by value,
// ...
auto lambda2 = [=,this]{ use(i,x); }; // BAD: not much better, and confusing
auto lambda3 = [&,this]{ use(i,x); }; // BAD: not much better, and confusing
auto lambda4 = [&]{ use(i,x); }; // BAD: if lambda2 leaves the scope, it contains a dangling reference to the this parameter from this function's invocation
// ...
auto lambda5 = [i,this]{ use(i,x); }; // ok, most explicit and least confusing
auto lambda2 = [i,this]{ use(i,x); }; // ok, most explicit and least confusing
// ...
}