Open LeonMatthesKDAB opened 1 year ago
Note that we would need to search for any #[doc = "..."]
attributes on existing syn blocks then apply these to the generated C++ code.
Also questionable what to do for a documentation on a #[qsignal]
, as that's then declared both in C++, as well as Rust.
Should that show up in both C++ and Rust?
Then what does Rust end up doing with the @arg tags, etc.?
Potentially partially implemented in #1054
We should consider supporting user documentation on the generated C++.
So if someone writes:
The
A documentation comment
should be exported as a Doxygen-compatible documentation comment into the generated C++ code.