Currently, when the analyzer wants to emit a report, it takes a naked pointer, and the emitReport function eventually takes over ownership of that pointer. I think this is a dangerous API because it's not particularly clear that this ownership transfer will happen, or that the pointer must be unique.
This patch makes the ownership semantics more clear by encoding it as part of the API. There should be no functional changes, and I do not think it caught any bugs, but I do think this is an improvement. Thoughts or opinions? ~Aaron
unique.patch
Description: Binary data
_______________________________________________ cfe-commits mailing list [email protected] http://lists.cs.uiuc.edu/mailman/listinfo/cfe-commits
