Ben Visness

I think that would more or less put us back where we started. I'm fine with the terminology in this PR even though `open` and `final` are not perfect opposites....

Further bikeshed options: `ext` and `noext`, `sub` and `nosub` (lol)

To readers of the text format, I think the word `sub` simply seems to indicate a list of super types. I read it like "subtype of foo". It doesn't appear...

@sbc100 Should the following two issues be added to this checklist? - #29 (explicitly marked as release blocker) - #67

@sbc100 More issues / PRs that I think should be on this list: - https://github.com/WebAssembly/memory64/issues/76 - https://github.com/whatwg/webidl/issues/1426 There are also the other scattered spec PRs I've been working on, but...

Yep, I've seen this before - fun fact, when I showed my coworker, the very first thing he did was perfectly reproduce this bug 🙃 What's happening is that I...

Yep, for sure, it's just a holdover from an earlier time. At this point my keyboard editing stuff is good enough that I think I can just render an empty...

After today's CG discussion, I think it makes more sense to keep the `@name` annotation, since it doesn't seem like identifiers will ever be able to express the full range...

I'm not personally clear on how much trapping we allow during races on shared memories, but it would certainly help to clarify a lot of design issues. Our prototype of...

As for `memory.discard` - while it would be a useful add-on for "traditional" linear memory, I'm not sure it has much place in mappable memories. You could generally achieve the...