Usage of import/export is confusing and should be hidden
alexcrichton opened this issue · 1 comments
Right now all language bindings (and the CLI) support import and export modes. Figuring out what this means within each language generator is confusing and easily forgotten. I don't like how this has shaped up. Internally I think this distinction is necessary for configuring what sort of bindings are generated where, but ideally this would not be a concern of an end-user.
I'm not sure how to fix this though since *.witx files are fundamentally only intended to describe "half" where they're describing either what a wasm module is importing or what a wasm module is exporting. Hosts may want to prefer to say "here's the adapter module that I'm working with" and have everything generated from that. Wasm programs seem like they still want to separate imports/exports, though.
That may actually be the fix? We could have hosts deal with imports/exports all at once where you just say "here's the shape of the wasm module I'm generating bindings for" but the import/export terminology and split sticks around for guests compiled to wasm.
In any case I haven't given this too too much thought but I wanted to at least jot down some ideas and the fact that this is an issue I'd like to fix.
I'm going to close this in favor of #314 and the advent of *.world files.