Proposal: Integration of WASM Exports Simulation for module build with go and GOOS=wasip1

[juliens]

Hello,

I am currently working on a project that involves simulating WASM exports in module compiled with the Go compiler and GOOS=wasip1.

My simulation system is based on an infinite loop in the "main" function. This infinite loop wait by calling a function on the host that use a chan to propagate the needed callback the guest must call and it uses some more functions to forward input args and return values. ( here is a WIP proof of concept https://github.com/juliens/wasm-goexport )

Would your team be open to accepting a pull request that adds this integration to the http-wasm project?

[jcchavezs]

Hi @juliens! Thanks for coming by.

While I think this is great stuff, I also believe this is somehow specific to host it in this repository. I suggest have a repository dedicated to that concept instead.

Keep the great work.

[juliens]

Hi @jcchavezs,

Thank you for your feedback and your kind words.

I completely understand your point about keeping the repository focused. My goal is to make my library as transparent as possible, but there are still some issues that require changes in http-wasm.
For example, with my implementation, the ExportedFunctions are not available at the time of compiling the module, but rather when the _start function is called.
Currently, your code performs checks on the exported functions, which prevents a straightforward integration of my library.

I wonder if you would accept some minor change ( which should not impact user experience ) to handle those kind of problem.

I appreciate your consideration and any advice you might have on how to address these challenges.