Dynamic Linking: imports module name

Hello,

I have been experimenting with wasm dynamic linking, and have a question. If I define a module foo which depends on the function f in module bar, using the --shared linker flag bar gets put into the dylink section of foo. The function f gets put in the import section along with the other needed globals and memories etc. However, the module name argument of the import of f is env, and not bar. So the import becomes env.f and not bar.f.

Is this intended behaviour? And if so, why? I would expect the module name for the import to be the actual name of the module the import originates from. It also seems logical to have the module name env reserved for imports that the interpreter provides, such as functions to interact with the interpreter.

Start by reviewing the dynamic-linking behavior described for the dylink and import sections, focusing on why the imported function uses the env module name instead of bar. Determine whether this matches the tool-convention expectations and document the intended behavior and rationale, or identify the convention change needed.