Guy Bedford

Try adding the `--no-wasi-shim` flag. The WASI bindings are automatically mapped using mapping configuration - https://github.com/bytecodealliance/jco/blob/main/src/cmd/transpile.js#L92. The bug here is that TypeScript output does not yet support the `map` configuration...

@Mossaka in the JS bindgen we special case top-level errors as being idomatic (try-catch), as distinct from other Result positions. Perhaps something similar might apply to Go?

> You still need a representation of results that works in places other than the outer-most return type of a function In JS, we use the standard tagged error object...

Nice to see this fleshed out proposal. Having to deal with None v Some branches in all places where things are optional does create overhead that is nicer to avoid...

Ah I missed that there was that `"exports": String` sugar... that sounds useful. I guess it's mostly an aesthetic argument at this point about the `""` case.... say you were...

Maybe we should just got back to `default`? Reserving a real value really doesn't seem that bad to me - we can just throw an invalid package specifier for any...

I would prefer to disallow the empty string so that it is simpler to explain to users. Even though it’s algorithmically an exception it wouldn’t be seen that way by...

@GeoffreyBooth it's great that you're thinking in terms of the Kolmogorov complexity of the spec, but we are optimizing for user experience + spec complexity, not for one over the...

I think this is more of a modules issue than being directly related to this proposal at this point. Whether this proposal implements the dot main or not seems separate...

In IE11 you must explicitly include a Promise polyfill in SystemJS. See https://github.com/systemjs/systemjs#polyfills-for-older-browsers.