Currently, comments written on Nim declarations annotated with {.ffi.} are lost during conversion. They don't survive into the generated
output for the target language.
Feature request: let the author write comments alongside the {.ffi.} annotations in the Nim source and have those comments carried through the codegen so they appear in the final product (e.g. the generated C header / target-language bindings).
This lets us document the exported API once, at the source, and have that documentation reach consumers of the bindings without maintaining a separate copy.
vacp2p/nim-libp2p#2774 (comment)
Currently, comments written on Nim declarations annotated with {.ffi.} are lost during conversion. They don't survive into the generated
output for the target language.
Feature request: let the author write comments alongside the {.ffi.} annotations in the Nim source and have those comments carried through the codegen so they appear in the final product (e.g. the generated C header / target-language bindings).
This lets us document the exported API once, at the source, and have that documentation reach consumers of the bindings without maintaining a separate copy.
vacp2p/nim-libp2p#2774 (comment)