1250714 - Baldr: Empty export name strings are not handled correctly.

Status: RESOLVED INVALID

(Core :: JavaScript Engine: JIT, defect)

Description

[Michael Bebenita [:mbx]]

print(Object.getOwnPropertyNames(wasmEvalText("(module (func (result f32) (f32.const 0x1.91p+2)) (export \"\" 0)(export \"foo\" 0))")));

prints: "foo,prototype,length,name", the "" empty property is missing.

Comment 1

[Benjamin Bouvier [:bbouvier] (inactive)]

That's intended, at the moment: the empty property means the default export, so that calling the result of wasmEval will just call the default export.

The rules we implement are the following:
- either the module has no default export, in which case an object is returned. Keys (resp. values) are the exports' names (resp. functions).
- or the module has a default export, in which case a function is returned. Then other exports are properties of the returned function. This is what you're seeing in your example.

The intent is to work like ES6 modules: `import Module from './mymodule.wasm';` would just bind Module to the default export, whereas `import {named} from './mymodule.wasm';` would bind `named` to the export called "named" in the module.

Comment 2

[Michael Bebenita [:mbx]]

Ahh, okay, that makes sense. Thanks for the explanation.