Andreas Rossberg
Andreas Rossberg
The fundamental problem with throws-annotations -- which essentially are a form of effect type system -- is that they are largely impractical in the presence of anything higher-order, like objects...
Well, so far polymorphism has not been on the table for Wasm (though I think GC types will eventually necessitate it). Let alone first-class polymorphism, which is what you would...
Okay, that's interesting. :) How will that work if two modules share a mutable funcref global or a table? A funcref can tunnel through those without giving the interface layer...
But the question is: how would they prevent it? The only way I can see is by not allowing higher-order state in an interface, i.e., no mut globals or tables...
@Serentty: > I’m curious why the proposal specifically only allows immediate values for to specify the address space. Why complicate the implementation of fat pointers like this? It's the difference...
@conrad-watt, friendly ping.
@conrad-watt, ping again. ;)
@conrad-watt, ping ping ping.
Weird, I can't seem to reproduce or find the rendering errors you mention. The PDF build also works fine. Where exactly do you see them?
That is weird, the HTML displays perfectly fine for me, both in Safari and Chrome. Which version of Chrome is yours?