Hi, Anna. When you get the chance, can you look over my patch for <rdar://problem/13405162>? It seems like a straightforward idea, but I'm not sure if there are any questions about the implementation.
> [analyzer] Model trivial copy/move assignment operators with a bind as > well. > > r175234 allowed the analyzer to model trivial copy/move constructors as > an aggregate bind. This commit extends that to trivial assignment > operators as well. Like the last commit, one of the motivating factors > here > is not warning when the right-hand object is partially-initialized; this > can have legitimate uses. > > Unlike r175234, which modified ExprEngine, this change is implemented as a > checker (CXXTrivialAssignmentChecker) using the old evalCall callback > mechanism. This seems cleaner than adding more special cases into > ExprEngine > and once we've designed a CallEvent-based interface for evalCall, we can > migrate the constructor case to this as well. Thanks, Jordan
trivial-assignment.patch
Description: Binary data
_______________________________________________ cfe-commits mailing list [email protected] http://lists.cs.uiuc.edu/mailman/listinfo/cfe-commits
