zokrezyl wrote: > Great, thank you! > > > IMHO: I guess a relevant test case is to take some huge relevant project, > > maybe LLVM itself and parse all their files and walk through all the nodes > > of the ast through all the members/methods recursively > > The problem is that this depends on the functionality you're testing, e.g. in > this case, just walking the entire Clang AST would not have been enough to > detect the issue, you would have had to call `cursor.type.kind` for every > node. And at that point, you might as well compare the possible to the mapped > kinds directly.
Well, that is what I mean walking recursively and calling all possible methods, attributes, at least those that do not need arguments. Obviously avoiding cycles, as such a walking would cause cycles. https://github.com/llvm/llvm-project/pull/142634 _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
