[cfe-dev] [cfe-commits] r126459 - in /cfe/trunk: include/clang/AST/ include/clang/Frontend/ include/clang/Serialization/ lib/AST/ lib/Sema/ lib/Serialization/ test/Index/ tools/libclang/

[Craig Silverstein]

} It's basically done.

Are there any immediate plans to move QualifiedTemplateName and
DependentTemplateName to expose NestedNameSpecifierLoc instead of
NestedNameSpecifier, or will that wait for sometime later?

} > It looks like the only place where we still can't use
} > NestedNameSpecifierLoc is QualifiedTemplateName/DependentTemplateName.
} > While there's still some work to make some of the other types
} > loc-aware -- TemplateSpecializationType only provides access to
} > TemplateArgument, not TemplateArgumentLoc, for instance -- we're
} > getting ever-closer to the day when RecursiveASTVisitor will be
} > entirely loc-aware!  I'm excited.
}
} TemplateSpecializationType doesn't have a nested-name-specifier in it; there will be an ElaboratedType around the TemplateSpecializationType to capture the nested-name-specifier.

Sorry if I wasn't clear -- I had changed the subject in the second
paragraph a bit to talk about other location-aware types.  For
TemplateSpecializationType, it's TemplateArgumentLoc (right now, TST
only exposes TemplateArgument).

There are a few other places that we don't have access to the *Loc()
variant of a structure (Type, TemplateArgument,
NestedNamespaceSpecifier), but not that many!

craig