What's the idea behind the API design of the import! macro? #38
Description
So I'm able to understand that bindings are generated by the export! macro so that when the code is compiled to WASM, one is able to use the functions written in Rust to match the signature of the WAI syntax.
However, I don't understand how exactly the import! macro does. Sure, it generates the bindings so you could call the function but .wasm file with the actual code to be able to execute it. Where does that come from exactly because the current API seems to provide the functions directly, it seems.