Advance to Phase 3?

[aheejin]

I think we have met all entry requirements of Phase 3:

• We tied some remaining loose ends in the core spec: Remove unwind #156, Allow catch/delegate-less trys #157, Replace 'event' with 'tag' in explainer #161, and Make attribute's encoding uint8 #162
• We updated JS API spec: [js-api] Add description of interface additions to overview document #154
  (It looks [js-api] Add specification. #86 is not up-to-date yet, but I don't think we need the formal notation to enter Phase 3)
• We added spec tests: [js-api] Add spec tests for proposed API additions #155 and [interpreter] Parse and convert EH opcodes #160

Some of these PRs have not landed yet, but I expect them to land within a few days.

One thing that we didn't reach consensus of is finally support (#158), whose discussion seems to be stalled at the moment. I'm not sure if we can agree on semantics in near future, given that it is not a simple feature. I'm more willing to defer its support to a potential follow-on proposal than holding the whole EH proposal back from advancing to the next phase.

If people agree, I'd like to propose the phase advancement in the CG meeting within a few weeks. What do you think?

[aheejin]

I added an agenda item to advance the proposal in the next CG meeting (7/20). (7/6 meeting will be cancelled because it is a holiday.) WebAssembly/meetings#811

[aheejin]

We advanced the proposal to phase 3 in 7/20/2021 CG meeting.