5 Commits

Author	SHA1	Message	Date
Richard Smith	c38498f046	PR23334: Perform semantic checking of lambda capture initialization in the right context. ... Previously we'd try to perform checks on the captures from the middle of parsing the lambda's body, at the point where we detected that a variable needed to be captured. This was wrong in a number of subtle ways. In PR23334, we couldn't correctly handle the list of potential odr-uses resulting from the capture, and our attempt to recover from that resulted in a use-after-free. We now defer building the initialization expression until we leave the lambda body and return to the enclosing context, where the initialization does the right thing. This patch only covers lambda-expressions, but we should apply the same change to blocks and captured statements too. llvm-svn: 235921	2015-04-27 21:27:54 +00:00
Aaron Ballman	6c93b3e29c	Adding a -Wunused-value warning for expressions with side effects used in an unevaluated expression context, such as sizeof(), or decltype(). Also adds a similar warning when the expression passed to typeid() *is* evaluated, since it is equally likely that the user would expect the expression operand to be unevaluated in that case. ... llvm-svn: 224465	2014-12-17 21:57:17 +00:00
Eli Friedman	4e28b26589	sizeof(void) etc. should be a hard error in C++. ... PR16872. llvm-svn: 188324	2013-08-13 22:26:42 +00:00
Douglas Gregor	656bc62a73	Remove the "unsupported" error for lambda expressions. It's annoying, ... and rapidly becoming untrue. llvm-svn: 150165	2012-02-09 08:26:42 +00:00
Douglas Gregor	8962549164	Implement C++ [expr.prim.lambda]p2, which bans lambda expressions in ... unevaluated operands. Be certain that we're marking everything referenced within a capture initializer as odr-used. llvm-svn: 150163	2012-02-09 08:14:43 +00:00