[PATCH] Fix PR20619 - failure to define implicit copy ctor of a by val capture in a generic lambda
richard at metafoo.co.uk
Wed Dec 3 13:02:52 PST 2014
>>! In D6171#5, @faisalv wrote:
>> We shouldn't mark the operation as used if the generic lambda itself appears in a dependent context. I would strongly prefer that we set the CurContext to the context surrounding the generic lambda before processing an implicit capture to handle that case.
> But I thought this patch won't mark it as used if the enclosing context is dependent - since I explicitly check for that - what am I missing?
It's still the wrong way to do this. Rather than working around the context being wrong, you should switch to the right context before building the copy.
More information about the cfe-commits