Francis McCabe

Handling callbacks (sic) is an explicit aim of the interface types proposal. At the moment, there is no specific plans to specifically support promises; we imagine that there may be...

If I understand correctly, you are 'pushing' both the field names and values on the intermediate stack. I would suggest a different approach, think of the signature of the record...

Personally, I am not very familiar with LSP. Generally, just because *some* IPC schema languages support recursive types (it is obviously possible to support them) does not mean that we...

There may be some additional misconceptions here. We do not just 'ban' recursive types. In the base Interface Types language, it is not possible to define any new types. This...

@badeend neither. Although circular structures are definitely not wanted. It has more to do with the intended scope of interface types. Recall that values are coerced across the function boundary....

Thanks for the thoughtful note. You should realize that so long as rust is based on linear memory it’s unlikely that there will be a zero cost mapping. Also asking...

I do have an additional thought wrt strings. If the strings the rust app is sending to the API are 'enum' values, then the web/host/wasm-IDL bindings story will have a...

The Interface Types proposal will have a method (sic) for doing this.

Concur! I would say that the current PR does represent a mini-MVP anyway.

>The exported functions of modules it links with must include those same error conditions in the return types of their exported functions. This appears to signal a misunderstanding of the...