There is some confusion on what the differences are between C lib interop, and WASM Interface Types interop, IF K/W's WASM interop expands to include these options.

1. I’m not sure about bidirectional C interop, maybe. No concrete plans. 2. They are different layers. 3. You would want a wasm object file + header file. 4. No concrete plans for interoperation with other languages compiled to Wasm at the moment. 5. Not yet.

I get the impression with the WASM object file + header file system that the C interop process (with generating the mapping files) would be extremely similar to how K/N does it, but the linking process would be completely different. If my understanding is correct, the header files provide the interop metadata to generate the mapping files, and the WASM object files provide the linking metadata to generate the WASM module (roughly equivalent to an ELF file). 🤔

This is what I am referring to with the C interop (also covers how manual memory management works alongside K/N's GC based memory model): https://kotlinlang.org/docs/native-c-interop.html