I'd be surprised if this interface worked well for the libclang backend - I expect its output is something in principle similar to XML DOM tree and you can't capture the tree with a simple array of tags unless you want to give up some information (which I'm afraid will be necessary for e.g. better autocompletion).

The way of libclang is the same for almost every (library that provides a) compiler front-end. I've never seen one that doesn't represent the parsed code as an abstract syntax tree. If TagManager can't support that properly, then it won't support most languages properly.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.