Ben Visness

I'll take a crack at it and get back to you. For what it's worth, I would really prefer option 3 in the long term. But, I think it would...

> It was pointed out to me that the current spec for table.get and table.set in the JS API might be lacking calls to ToWebAssemblyValue for the index argument. I...

Assuming it doesn't need to be in the main spec today, I can do that as part of my other memory64 spec updates.

The SpiderMonkey implementation has landed in Nightly: https://bugzilla.mozilla.org/show_bug.cgi?id=1893643 Aside from the concerns laid out in #68, our implementation is ready for phase 4.

What's wrong with "index type"? I haven't been following #50 very closely, but I struggle to think of a better term generally. If it were only memories, you could call...

If I'm understanding correctly, the spec today currently doesn't choose an official name like "index" for the parameter to `table.get`, but I think "index" is clearly implied - the execution...

I've been making a variety of spec updates in #71, and would be happy to change "index type" to "address type" as part of that PR if people agree. Any...

I'm working on a PR for this issue. This is an almost invisible change to users except for one thing: the `index` parameter on table and memory descriptors, used in...