Suggestion: handling of mixed typedef and struct definition

[pierre-24]

Linked to #35

In C (it is not the case in C++), it is customary to do

typedef struct stuff_ {
  int a;
} stuff;

If doxide encounter such construct, it seems to be creating a page for struct stuff_ and forgets about the typedef. It would probably be possible to automatically duplicate this info and create an corresponding entry for the corresponding typedef structy stuff_ stuff.

However, that's a C specific stuff, so I understand if it is not a priority :)

[lawmurray]

This is great feedback, thanks. And I would like to make C support a priority, so any contributions to improve parsing and output for C would be happily received. I think this one wouldn't be too tricky to support, the tree-sitter query (even though it's for C++, as much as possible would be good to reuse it for C) likely just needs to catch the common use case of a the typedef around a struct declaration and set up the data structure of entities accordingly.