c-api: expose tail call configuration option in c api

[womeier]

The tail call proposal configuration is not yet exposed by the C api.
This change intends to allow configuring the option in e.g. the python library bindings:
bytecodealliance/wasmtime-py#204

I wanted to test this change doing the following:

Following the docs, I ran
cargo build --release --manifest-path crates/c-api/Cargo.toml which should place libwasmtime.{a,so} in target/release.
The command succeeded, but the file is not generated (and I cannot find libwasmtime.so with find).

I thus didn't test the change further than the fact that it compiles, in particular I didn't yet test the change
with the python library.
Tested to work together with the PR: bytecodealliance/wasmtime-py#205 adjusting the python bindings.

[alexcrichton]

Looks great to me, thanks! Apologies for the documentation but it's outdated. Nowadays the correct invocation is with -p wasmtime-c-api instead of --manifest-path .... I'll send a separate PR to update those docs.

[github-actions]

Subscribe to Label Action

cc @peterhuene

Details

This issue or pull request has been labeled: "wasmtime:c-api"

Thus the following users have been cc'd because of the following labels:

• peterhuene: wasmtime:c-api

To subscribe or unsubscribe from this label, edit the .github/subscribe-to-label.json configuration file.

Learn more.

[womeier]

Thanks for the quick response @alexcrichton!

I created a PR with the changes to the python bindings, they work as expected together, i.e. I can run my wasm module with tail calls using the python lib :)