Joel Dice

I'm also wondering if it should take a `client` parameter, in case the guest wants to use it e.g. to publish new messages to the same client it received the...

> So for the channel part of this, that is part of the message itself and I think that is a fairly easy thing to consume. Sorry, I'm not quite...

Thanks for clarifying -- that works for me.

Just wanted to chime in and say this all sounds good to me. Thanks for writing it up! I'm happy to implement the short-circuit workaround for existing modules if nobody...

@alexcrichton We could generalize the logic I added in https://github.com/bytecodealliance/preview2-prototyping/pull/83 and https://github.com/bytecodealliance/wasm-tools/pull/919 such that wit-component wraps the main module's cabi_realloc function in some code that sets the `allocation_state` global (and...

BTW, will this be an issue for post-return functions also?

I discussed this with @sunfishcode and @lukewagner today, and I think the plan going forward is to move away from wrapping each export in ctor/dtor calls and instead rely on...

(I'll let Luke or Dan answer your first question, since they floated a few ideas, and I'm not totally sure where they landed). > Can you describe more what "handle...

> How plausible is it to change wasi-libc just not call any import functions in its constructors? Probably doable for environment variables, but not sure about preopens.

> I don't understand how this approach is viable, because short-circuiting the response to wasi-libc gives it incorrect values. How do those values later get corrected when calling imports is...