Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Time to write documentation? #153

Open
Hywan opened this issue Sep 22, 2020 · 2 comments
Open

Time to write documentation? #153

Hywan opened this issue Sep 22, 2020 · 2 comments

Comments

@Hywan
Copy link
Contributor

Hywan commented Sep 22, 2020

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.

@peterhuene
Copy link

For what it's worth, Wasmtime tries to document the part of the C API it supports. It's generated from this file which, unfortunately, has to be maintained separately from wasm.h.

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?

@Hywan
Copy link
Contributor Author

Hywan commented Sep 29, 2020

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants