Ability to combine two import objects about wasmer

[tprk77]

I just updated my project to use the new extend. Very nice, seems to be working great. 🎉

[bjfish]

@lachlansneff What would you think about representing imports object during instantiation with something like the following?
Vec<(String, String, &Export)> or a struct instead of a tuple. I used &Export here so that the user code can own the export (not move it) and we can clone it during instantiation.

If there were duplicate module/name pairs that would result in an error.

[tprk77]

I want to apologize for my somewhat curt issue description. I was just a bit disappointed that my PR was not going to get merged. But I don't have the same insight into the project, so it's very understandable if there's another solution in mind. (It's your project after all. 😁)

To illustrate the functionality I'm looking for, it might help to show my usage:

https://github.com/tprk77/experiments_in_ros2_rust_and_wasm

Specifically, these lines:

https://github.com/tprk77/experiments_in_ros2_rust_and_wasm/blob/2fce069622477fdb795d839349185650019ccb63/ros2_ws/src/ros2_rust_wasm/src/main.rs#L54-L65

I have two versions of the same "app," one in Rust and one in C++. I want to expose the same API imports to both. But to get the C++ app working, I also need the Emscripten imports. (ros::get_imports() is returning an ImportObject containing a ROS2-like API.)

The actual mechanism doesn't really matter to me, but it would be nice if I could still use the imports! macro because it's so convenient. My concern at the moment is with Emscripten, but I think there's also a more general issue of what to do when there are multiple import objects corresponding to multiple APIs. For example, if the mod sensors supplies an import object for a Sensor API, while the mod motors supplies an import object for the Motors API, how to we use both in the same instance?

[lachlansneff]

@tprk77, we're really sorry about not being responsive enough with your other issue. Things have been quite busy here. I'll make sure to take a look at this pr tomorrow morning.

[MarkMcCaskey]

That's great! We're glad to hear that.

Thanks for your PR by the way, it helped me get adjusted to the Wasmer code base! Best of luck with your project and let us know if there's anything we can do for you to make using Wasmer better!