Possible incorrect generation of returns documentation

[jackt-swf]

Hello and thank you for this awesome repo, it's made generating FFI's much easier for me.

I am having an issue when transforming doxygen's \return.

If given this doxygen comment:
\\return DPFPDD_SUCCESS: Library was initialized;\n\\return DPFPDD_E_FAILURE: Failed to initialize library.

Which looks like this:

Returns
    DPFPDD_SUCCESS: Library was initialized;
    DPFPDD_E_FAILURE: Failed to initialize library.

doxgen-bindgen::transform outputs:
# Returns\n\nDPFPDD_SUCCESS: Library was initialized;\nDPFPDD_E_FAILURE: Failed to initialize library.

Which looks like this:

Returns
DPFPDD_SUCCESS: Library was initialized; DPFPDD_E_FAILURE: Failed to initialize library.

What I am wonder is if its possible to format multiple \returns similar to how \params are formatted, as a list, like such:

Returns
DPFPDD_SUCCESS - Library was initialized;
DPFPDD_E_FAILURE - Failed to initialize library.

[jackt-swf]

Also, something I might add, are the headers for arguments, returns, etc, are quite large due to the usage of markdown's h1 (#). Maybe consider using ## or even ### instead?

[Jisu-Woniu]

Also, something I might add, are the headers for arguments, returns, etc, are quite large due to the usage of markdown's h1 (#). Maybe consider using ## or even ### instead?

In rustdoc, titles of sub-sections always starts with <h1>, then <h2>, <h3>, ... If you think the default h1 style is too large for you, maybe you should consider setting your browser or your CSS.

An example may be found from std's doc:

https://doc.rust-lang.org/stable/src/core/num/int_macros.rs.html#460-471