On Jun 3, 2013, at 8:11 PM, Stephen Lin <[email protected]> wrote: > Here's a freshly rebased pair of patches. > <this-return1.patch><this-return2.patch>
I don't understand why EmitConstructorCall needs to take a ReturnValueSlot or return an RValue. There's one call site, and it passes an empty ReturnValueSlot and ignores the result. This seems to just be cluttering the API. Is there a reason why these patches are separated? (Did I ask for that for some reason?) John. _______________________________________________ cfe-commits mailing list [email protected] http://lists.cs.uiuc.edu/mailman/listinfo/cfe-commits
