You can share a Nim source file containing only the procedure headers. What the
body of those procedures should be is up for debate. What comes to mind is
leaving the body empty and specifying a `importc` and `dynlib` pragma which
imports a Nim DLL built by you.
Something in the language to mak
I have a question about following Nim compiler/language use case: suppose, I
created a library and want to share it's functionality with others. But, I do
not want to share the source code, but just a binary distribution plus an
interface. This use case can be solved by creating a C-header file
