Hi Richard, Could you take a look at this patch? I haven’t messed with capturing in a long time and I don’t want to break it ;-)
Don't mistakenly capture byref in block nested in lambda
Even if an enclosing lambda captures a variable by reference, we capture
it by *copy* in a block unless the variable itself was declared with a
reference type. Codegen was already correct, but we were not diagnosing
attempts to modify the variable in Sema.
This also fixes a crash on invalid when trying to modify a variable with
non-trivial copy constructor and assignment operator in such a
situation.
block-in-lambda.patch
Description: Binary data
_______________________________________________ cfe-commits mailing list cfe-commits@cs.uiuc.edu http://lists.cs.uiuc.edu/mailman/listinfo/cfe-commits
