I'm working on a project that has a C header documented with Doxygen and a Rust portion that generates bindings for the header using bindgen. The rustdoc documentation extracted from the C header is pretty bad. (It includes some Doxygen commands like "@brief", misparses struct element documentation, etc.) What are the best practices here? Should I run bindgen by hand and edit the documentation, or just get rid of Doxygen entirely? What is the best way to document C code in a rustdoc-friendly way?
This topic was automatically closed 90 days after the last reply. We invite you to open a new topic if you have further questions or comments.