You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For the moment, it is assumed that the project does not provide any documentation. When will it be time to write documentation, and did you already think about the format to use? Will it include examples?
I would be happy to write such documentation. Wasmer now provides a compatible C API to wasm-c-api, but we lose all the documentation and examples that we wrote for the users (see 1 or 2).
Thanks.
The text was updated successfully, but these errors were encountered:
The documentation above is Wasmtime-specific since it only covers what is implemented by Wasmtime, so I'm not advocating for using it to document the full C API. Perhaps, instead, we could document wasm.h itself using the same doc comment format so popular tools such as Doxygen can be used to generate the documentation?
Wasmer already uses Doxygen to document the existing C API. But I didn't want to mix with a side .h file. Hence my question to document wasm.h directly.
Hello dear all,
For the moment, it is assumed that the project does not provide any documentation. When will it be time to write documentation, and did you already think about the format to use? Will it include examples?
I would be happy to write such documentation. Wasmer now provides a compatible C API to
wasm-c-api
, but we lose all the documentation and examples that we wrote for the users (see 1 or 2).Thanks.
The text was updated successfully, but these errors were encountered: