I’m currently writing a Tool using libtooling & RecursiveAstVisitor.
In the AST I come across quite a lot of Unresolved expressions and I looked through the documentation of UnresolvedMemberExpr [UnresolvedMemberExpr] there it says that those nodes will be resolved in the final AST.
Is there any possibility to get this final AST and run the tool over this? Or to what does this refer?
I'm currently writing a Tool using libtooling & RecursiveAstVisitor.
In the AST I come across quite a lot of Unresolved expressions and I
looked through the documentation of UnresolvedMemberExpr
[UnresolvedMemberExpr]<http://clang.llvm.org/doxygen/classclang_1_1UnresolvedMemberExpr.html#details> there
it says that those nodes will be resolved in the final AST.
Is there any possibility to get this final AST and run the tool over this?
Or to what does this refer?
The AST you see with libtooling should be the final AST Are you running
over incomplete code (that is, code that doesn't compile)?
I've not checked, but I'd assume that there are plenty of unresolved
nodes in parsed templates (as opposed to their instantiations).
Likely the documentation could be improved.
However if I enter a value instead of the typeId function it is no more unresolved.
So I guess this is normal behavior (because of template stuff) and therefore the description is wrong?