Details
Diff Detail
- Repository
- rC Clang
Event Timeline
Mostly looks good (a few minor nits), but I did have a design question about whether we should prefer calling a Visit method for type hierarchies instead of reimplementing the functionality.
lib/AST/ASTDumper.cpp | ||
---|---|---|
145 | Why this approach instead of deferring to VisitArrayType() as before? I prefer calling the Visit function rather than reimplementing the functionality because we may decide to later improve the base class printing and expect subclasses to automatically pick that up. WDYT? | |
164 | Why this approach as opposed to deferring to VisitFunctionType() as before? | |
lib/AST/TextNodeDumper.cpp | ||
14–16 | Remove newline | |
960 | It'd be nice to remove this use of auto. | |
971 | It'd be nice to remove this use of auto. | |
1047 | It'd be nice to remove this use of auto. |
lib/AST/ASTDumper.cpp | ||
---|---|---|
145 | I think it's more clear to read what each visit method does, but I don't feel strongly about it. I can change this if you do. |
lib/AST/ASTDumper.cpp | ||
---|---|---|
145 | Given that there's an established type hierarchy, I prefer calling the Visit() function for the superclass rather than reimplementing. The extra indirection wasn't too annoying with the old code, so it's unlikely to be too problematic with the new code (and if it is, then we'll have reason to change). |
Why this approach instead of deferring to VisitArrayType() as before? I prefer calling the Visit function rather than reimplementing the functionality because we may decide to later improve the base class printing and expect subclasses to automatically pick that up. WDYT?