Jeremy Maitin-Shepard

The current version that I have implemented only allows `///` commands and expects rST syntax, but additionally translates some doxygen commands like `\param` and `\returns`. Supporting other syntax would be...

That's interesting, I didn't know about the xml comment output from clang. I've been working on putting together an initial/draft version of the cpp apigen based on what I implemented...

To be clear --- is that XML output from clang or from doxygen? One of the nice things about the way I'm currently parsing doc comments is that line number...

What is it that you don't like about doxygen's grouping? The grouping feature I've implemented for the C++ and Python apigen extensions is certainly inspired by doxygen, though there are...

The way it currently works is that in the builder-inited event, which happens before sphinx actually reads any of the rst documents (or even determines the list of rst files)...

Currently there is no access specifier filtering, but entities without a doc comment are skipped. There can be more than one declaration but only one definition within a single translation...

The idea is that you arrange to include all the headers you want to document in a single translation unit (i.e. unity build), that way every header is parsed only...

> > The idea is that you arrange to include all the headers you want to document in a single translation unit (i.e. unity build), that way every header is...

> I wish clang would expose a way to filter AST by relativity to indexed unit. What do you have in mind as far as relativity?

That could be done with the `allow_paths` option but is basically the opposite of what I intended as far as the unity build approach, unless your library defines everything in...