5 Commits

Author	SHA1	Message	Date
Richard Smith	fa0a1f531f	Improve diagnostics for invalid use of non-static members / this: ... * s/nonstatic/non-static/ in the diagnostics, since the latter form outvoted the former by 28-2 in our diagnostics. * Fix the "use of member in static member function" diagnostic to correctly detect this situation inside a block or lambda. * Produce a more specific "invalid use of non-static member" diagnostic for the case where a nested class member refers to a member of a lexically-surrounding class. llvm-svn: 154073	2012-04-05 01:13:04 +00:00
Eli Friedman	c6237c6e05	Make the odr-use logic work correctly for constant-expressions. PR12006. ... llvm-svn: 151699	2012-02-29 03:16:56 +00:00
Douglas Gregor	81495f341d	Within the body of a lambda expression, decltype((x)) for an ... id-expression 'x' will compute the type based on the assumption that 'x' will be captured, even if it isn't captured, per C++11 [expr.prim.lambda]p18. There are two related refactors that go into implementing this: 1) Split out the check that determines whether we should capture a particular variable reference, along with the computation of the type of the field, from the actual act of capturing the variable. 2) Always compute the result of decltype() within Sema, rather than AST, because the decltype() computation is now context-sensitive. llvm-svn: 150347	2012-02-12 18:42:33 +00:00
Douglas Gregor	01db64f0ac	Add test from [expr.prim.lambda]p12, which deals with odr-use and ... nested captures. We currently don't get odr-use correct in array bounds, so that bit is commented out while we sort out what we need to do. llvm-svn: 150255	2012-02-10 16:48:36 +00:00
Douglas Gregor	f02455e5ee	Add various tests for captures and the reaching scope of the lambda ... expression. Implement C++11 [expr.prim.lambda]p12's requirement that capturing a variable will odr-use it. llvm-svn: 150237	2012-02-10 09:26:04 +00:00