Jesse van den Kieboom
Jesse van den Kieboom
1. Definitely want to have easy lookup to which header to include for a certain symbol. This is currently missing. 2. Having access to a list of symbols per header...
The `type` thing would be easy to change, but avoiding the explode of the template arguments is actually not currently possible in a reliable way due to how clang doesn't...
Yes, these situations are currently not really handled well with cldoc. There are some other things that would be nice, like only rebuilding docs for things that have actually changed...
I'm not sure I understand. A new section of what? cldoc does not support markdown titles as special segments, they are just going to be part of the documenting element....
Ideally, there would be support for some commented sections in markdown. The only thing that I found that people tend to do, is to use xml/html style comments (i.e. ),...
I don't want to hijack markdown semantics for special purposes. This also seems like quite a specific use case, so I'm not really willing to introduce yaml into the markdown...
This is currently not supported. The cldoc:begin-category thingies are only for sources, not for markdown files. I'm not sure if I want to add support for this, although I understand...
Just hiding all the options isn't a good solution in my opinion. Rather, they should be split over multiple lines.
Sounds good. PR welcome.
This feels a bit out of scope for flags (it's really not a flag anymore now). I can see why it's useful, I'm just not sure it belongs in go-flags...