Andreas Rossberg

Right. More abstractly, access is positive/covariant, while construction is negative/contravariant. For the former, an upper bound suffices, while for the latter, you need a lower bound.

The interaction of this proposal with custom page sizes is a good point! I think we have to make memory.grow/size use the index type to count pages in this proposal,...

> the abstract WebAssembly spec unconditionally requires a `u32` ([link](https://webassembly.github.io/spec/core/appendix/embedding.html#embed-table-read)) Ah, but this actually is an oversight. @sbc100, I think we need to update the embedder spec to use u64...

Unless there is a strong reason to do otherwise (like running out of bits), I think it's preferable to keep them in sync. (We have been doing the same for...

I have a request: can the documentation avoid the overuse of pattern matching and use the form `shared(msg)` for binding message contexts? I believe that is clearer and avoids the...

To be consistent with the (mainstream) style of writing parameters elsewhere. I'd probably use `msg`, because `msg.caller` seems intuitive and matches how it is named in other systems.

Good idea. We should structure it along the lines of other proposals, i.e., a cont/ (or stack/) subdirectory, and separate wast files per instruction tested, where possible.

So far, validation and execution isn't split anywhere.

@bvisnuss, `i` is universally used for integers. I'd prefer avoiding overloading terminology in potentially confusing ways. We already use the term "index" for all the index spaces, and in particular,...

Address type (addrtype) sounds good to me.