Sorry, I haven't commented because it looks like it's going to be less and less relevant to the analyzer. As much as I don't like having two similar data structures floating around, Edwin's right that we don't need to try to optimize for two different use cases if it means that we won't get optimal behavior in either.
This design is at least not incompatible with what the analyzer needs, in case we can ever unify them in the future. We may want to rename the analyzer's class StmtParentMap, and migrate the other users (migrators/translators) to AST's ParentMap. http://llvm-reviews.chandlerc.com/D267 _______________________________________________ cfe-commits mailing list [email protected] http://lists.cs.uiuc.edu/mailman/listinfo/cfe-commits
