Import/export matching by array position about wasm-c-api HOT 2 CLOSED

The current design is very intentional. Wasm doesn't specify what import resolution means, and hosts may use arbitrary strategies like e.g. materialising modules/functions based on import names or type information. In general, that would require a callback-based mechanism (cf. #53), which in turn is difficult to handle, especially for foreign language bindings.

So the idea of the current design is that the embedder does the resolution outside in whatever way it sees fit and simply constructs an adequate vector for instantiation. That way the issue of import resolution is nicely decoupled while remaining fully general. Custom resolution abstractions can easily be built on top.

from wasm-c-api.

So the idea of the current design is that the embedder does the resolution outside in whatever way it sees fit and simply constructs an adequate vector for instantiation.

Yes, I was only proposing to change the import binding to be by name instead of by index. However, I see that multiple imports may have the same module+name, so that wouldn't work.

The problem for WAVM is that it doesn't keep track of import indices in memory: it splits the imports into an array for each kind. I suppose I need to add a map from import index to kind-specific index.

from wasm-c-api.