Ben L. Titzer

JavaScript has [WeakMap](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/WeakMap), which was designed specifically for this purpose. It should be fairly easy to use in the JavaScript embedding. Of course that doesn't help other embeddings, so the...

@sunfishcode I've always had the model in the my head that WASM managed data will be like SIMD in WASM: a fairly well-contained extension that defines new values, types, and...

Wasm is generally designed as a minimal abstraction over hardware, so the design pressure is to expose (standardized) versions of what is in hardware, and not build the next higher-level...

@rossberg What about a future where we allow initializing whole (acyclic) graphs of objects in const initializers? This would be very useful for, e.g. Virgil, where an initial heap is...

Sure, you can't denote cyclic data structures purely in the initializer and have to fix them, e.g. in the start function. But it's a worthwhile tradeoff because those back links...

Relocation is still cheaper than allocating the objects one-by-one and then writing their fields one-by-one, even if the majority of the heap were reference fields, which is of course very...

> Are you talking about a scenario where Wasm is compiled to native code off-line and then cached between entire runs? Yes.

As I remember from Luke's presentation, we currently disallow duplicate exports. What if we lift this restriction and allow duplicate exports? That opens the design space for module linking to...

I think what I could not express in the CG meeting is that I think the module linking proposal is trying to push down requirements from name-based linking into the...

No, I am not proposing positional linking. I agree that that would be very fragile indeed. But reflecting on the Jawa use case, and also on interface types, the thing...