Andreas Rossberg
Andreas Rossberg
@conrad-watt, that scope makes sense. However, I would suggest a somewhat more orthogonal extension to .wast scripts. For example, I could imagine a small set of new commands like ```...
Sounds plausible. In fact, I think it's equivalent: if you copy only the sharable parts, then an attempt to use something else will likewise result in an error (assuming we...
> In fact, if a child thread were to shadow/replace a shared thing copied from the parent with an unshared thing, a child-of-child could never access the parent's shared thing....
Actually, on reflection, I was only considering lexically scoped names. But there also is the "registry" used for resolving imports, which is more like a side table. For that I...
Yes, that's the idea.
@conrad-watt, none I would remember. I believe these stubs were left by binji. Feel free to give it a shot.
Since this is solely a JS side matter, the only suitable place to add such information would be the JS host binding section. But is it really necessary?
A couple of comments: - "Canonical" to me implies that there is _one_ representation (at least per storage kind, i.e., we can argue that something like a future memory attribute...
@conrad-watt: > @rossberg I'd argue that the "canonical" nature of the string ABI comes from fact that at the boundary between components, the `string` type is viewed as a list...
Good point, I'll archive it. I don't recall that we have any guidelines regarding this. Should perhaps be added to the howto?