Francis McCabe

not completely sure I understand this question. there *will* be an Interface Types analog for record types. It has not been completely nailed down, but the IT type signature for...

There are likely to be multiple domain specific types. I suggest that we do not try to add them in at this point. Time is probably even more difficult to...

Hmm. Originally, adapter fusion was something that was done by the host as part of the import process. In that world, one would not need to specially break out malloc/free...

This is a step further away from what we were originally thinking: that the adapter specification would be declarative. More problematically, it carries the risk that we will not be...

This split of local heaps + global heap implies that, for languages like Java, there will be nothing in the local heap. I am pretty sure that that was not...

Every language compiler is going to map the semantics of their language to wasm. In the case of Java, there will be a single heap for all threads. In the...

Having multiple 'gc memories' is already explicitly a potential requirement. This is very important for 'process-oriented' languages like Erlang. But is also potentially useful for Java (with multiple class loaders).

I am afraid that you are maybe both missing a key aspect of the problem. We are targeting interface types to the scenario involving limited trust. This is true for...

IMO, you do not need a specific 'weak import' concept if you use 'web interoperability bindings'. In the case where an actual import is not provided, you can provide a...

This is not forgotten. We currently have instructions for calling a function and for invoking a method. On Fri, Nov 22, 2019 at 2:49 PM Gus Caplan wrote: > Here...