55 Commits

Author	SHA1	Message	Date
Douglas Gregor	53a9bdf17e	Improve checking of explicit captures in a C++11 lambda expression: ... - Actually building the var -> capture mapping properly (there was an off-by-one error) - Keeping track of the source location of each capture - Minor QoI improvements, e.g, highlighing the prior capture if there are multiple captures, pointing at the variable declaration we found if we reject it. As part of this, add standard citations for the various semantic checks we perform, and note where we're not performing those checks as we should. llvm-svn: 149462	2012-02-01 01:18:43 +00:00
Eli Friedman	f49643ddce	Add an additional testcase for a lambda with implicit void return type. ... llvm-svn: 149034	2012-01-26 03:16:41 +00:00
Eli Friedman	34b49061aa	Refactor to share code for handling return statements between lambda expressions and block literals. As it turns out, almost all the logic can be shared. ... llvm-svn: 149031	2012-01-26 03:00:14 +00:00
Eli Friedman	73a040906d	More lambda work: semantic analysis of capturing 'this'. It's a bit complicated, but we have to be careful about when exactly captures are marked given PotentiallyPotentiallyEvaluated contexts. (Actually, it's not 100% correct yet, but it's close enough for the moment.) ... llvm-svn: 147723	2012-01-07 04:59:52 +00:00
Eli Friedman	44803326d4	Lambdas: semantic analysis of explicit captures. ... This patch (and some of my other commits related to lambdas) is heavily based off of John Freeman's work-in-progress patches. llvm-svn: 147706	2012-01-07 01:08:17 +00:00