Implement "export/import * from" about assemblyscript

[dcodeIO]

That's right, wildcard exports and imports are not handled yet. Going to take a look and marking this issue as enhancement until then :)

[torch2424]

Awesome, thank you! :)

[gustavomick]

Any workaround in the meantime?

[dcodeIO]

Normal imports and exports should work, as should imports and exports of entire namespaces. Just the wildcard isn't implemented yet.

[gustavomick]

Thanks what if I need to import a wasm,eg. compiled code from c++ to wasm then importing that to ts. Any viable way to make that work? Thanks.

[dcodeIO]

Linking wasms is a bit tricky currently. What I have in mind for this case is that the compiler could be provided with a base wasm, appending any additional code to it. would that work for your use case?

Other than that there are tools like wasm-merge that can combine multiple wasms into one, resolving imports agains exports. That could already work today, but last time I checked this didn't seem to work reliably.

[gustavomick]

@dcodeIO thanks sorry about the late answer, i currently on vacations :).

i was thinking about creating empty interfaces/type/mocks on typescript, using them from my main typescript code, then compiling to wasm and then replacing those mocks with real wasm implementations (that were previously compiled from c++ to wasm). that make sense? although not sure how to do that. if you have any suggestion will be helpful thanks.

[dcodeIO]

That should be possible as well. On the AssemblyScript side, you'd then have a .ts file that declares the exported interface of the other wasm, which the AS module then imports. On the JS side, you'd then provide the other wasm for this import and it should just work.

declare namespace MyCppModule {
  export function someFunction(): i32;
}

// use it
MyCppModule.someFunction();
...

And simply give { MyCppModule: myCppModuleInstanceExports } as an import when instantiating the AS module.

[gustavomick]

@dcodeIO im missing something in here, how do i compile so my typescriptfile.wasm get linked to my cppfile.wasm file instead of the linked to the ts mock?
i thought i would had to create a workaround script to merge them, replacing the mock with the real implementation, how that part should work?

[dcodeIO]

Merging, or real linking, might be more complicated because a linker will have to move around data segments, table elements etc. and update their indexes where used. There is wasm-merge which might, or might not, help.

My example above was based on the assumption that you'd then have two WebAssembly modules, with the exports of your cpp module being provided as imports to the typescript module.

[gustavomick]

ok ill try to read about this, thanks 👍

[torch2424]

Closed by #489 😄