WASM: Support for setting an imported function's module name #454
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I need to compile a WebAssembly program that imports functions from a host that uses a module namespace other than the standard
env
. I enhancedgo:export
to support this. For example, in addition to the default export (env
module)You can set the module using
//go:export [module] <name>
Alternatively, you can use a separate comment
//go:module <name>
in conjunction withgo:export
orgo:linkname
. I'm happy to make any tweaks to the argument format.I tried to run
make test
but got clang linker errors. I tested usinggo install
andwasm2wat
to print the imports of the compiled wasm.I believe this fixes #423.