Christof Petig

If you ever need to update wasm-tools (e.g. because of the tuple bomb prevention) this patch should work well enough, I just can't tell whether it is correct enough for...

With a lot more tests passing in https://github.com/cpetig/wit-bindgen/tree/work-in-progress and https://github.com/cpetig/wasmtime-adapter/tree/fixed-size-list , and support for fixed size lists in wasm-component-ld main, I am now confident enough that this patch is correct....

I now removed the changes from the release-0.7.0 branch, which I assume is branching off to a stable branch and not intended to ever get merged into main. This update...

In short: Good to merge :wink:

Right, so 0 would be the externally agreed invalid id (instead of the -1 I see in wit-bindgen code) It makes perfect sense but I wonder whether this is already...

Whether lazy value lowering can support returning into pre-allocated buffers equally well is a good question. I know that if caller and callee share the same maximum size the string/list...

My primary motivation for working on this is the (functional safety) requirement of deterministic execution time. The most straightforward solution is with dedicated pre-allocated buffers provided by the caller. [Return...

To be honest I never had adding limits to WASI in mind when I thought of this feature, but more specialized custom WIT interfaces which are fully controlled by the...

Oh, wow, this sounded like a small thing to do, but I found that the following things make it really large: - `definitions.py` has no way to create dummy data...

I don't think there is a perfect solution for strings due to encoding variation, but taking the maximum length as the number of u8s in utf8 and number of u16s...