October CG meeting agenda (at TPAC)

[binji]

Here are a list of the current proposals. Which of these shall we discuss at the upcoming in-person CG meeting at TPAC?

• Threads (champion @binji - phase 1)
  • Updates on memory model and spec (@conrad-watt and @rossberg)
  • Race between memory.grow and access
• Garbage Collection (champion @rossberg - phase 1)
• Bulk memory operations (champion @binji - phase 1)
• ECMAScript module integration (champion @linclark - phase 1)
• Tail Call (champion @rossberg - phase 1)
• Multi-value (champion @rossberg - phase 3)
  • Move to stage 4? (blocked on implementation)
• Reference types (champion @rossberg - phase 3)
  • Move to stage 4? (blocked on implementation)
• Host bindings (champion @lukewagner - phase 1)
  • Recap problem statement: direct calls to any Web IDL methods/accessors from wasm
  • Recap developments since TPAC last year: extraction of the Reference Types proposal
  • Short browser update on any browser implementation progress toward Reference Types
  • Given Reference Types, what's left for Host Bindings to do?
    • The following are still missing when calling Web IDL:
      • Pass/receive a non-undefined receiver
      • Call as a constructor
      • Opt into unsigned interpretation of i32/i64 when converting to Number/BigInt
      • Callbacks: function reference types + func.bind (+ WeakRefs)
    • With Reference Types factored out into the core spec, consider renaming to "Web IDL Bindings"?
  • Observation: the real value prop to use any of this (from browser POV) is fast Web IDL calls
  • So, proposal: let's define a milestone that combines Reference Types + Web IDL Bindings MVP
  • Some WebGL/Emscripten glue code can move into WASM bytecode; this will help fast Web IDL calls
  • How would this look in the source language?
    • Short recap of Rust wasm-bindgen
    • How would this look in other languages? Is there an opportunity to share/regularize backend tools?
• JavaScript BigInt to WebAssembly i64 integration (champion @littledan - phase 2)
• Web Content Security Policy (champion none - phase 0)
  • How does CSP affect postMessaging of Modules
• Non-trapping float-to-int conversions (champion @sunfishcode - phase 4)
• Sign-extension operators (champion @binji - phase 4)
• Type Reflection for WebAssembly JavaScript API (champion @tschneidereit - phase 1)
• Unmanaged closures (champion @erights - phase 0)
• Custom Annotation Syntax in the Text Format (champion @rossberg - phase 1)
• Fixed-width SIMD (champion none - phase 1)
• Exception handling (champion @aheejin - phase 1)

I'm guessing that we won't need any discussion on the phase 4 proposals.

If you are a champion of one of these proposals, please respond whether you are planning to go to this CG meeting to discuss your proposal.

I believe we will need some new champions for some of these proposals, so if you are a current champion and would no longer like to be, please respond here too.

[stoklund]

I have to step down as SIMD champion. New job.

[binji]

Thanks, @stoklund, I've removed you from the tracking issue.

[linclark]

I am planning to go to this CG meeting to discuss ES module integration.

[rossberg]

The topics I would like to discuss are

• Tail calls
• Garbage collection
• Memory model and spec for threads (with Conrad)

There are also the phase 3 proposals: multi values and reference types. These are currently blocked on implementation work in engines. If engines make sufficient progress by October then I'd like to discuss moving them forward to stage 4. Otherwise there probably isn’t much to discuss, though I could just give a 2 minute update.

As mentioned in a recent VC, I’m looking for somebody to help with or take over championing the JS type reflection proposal.

[littledan]

I'm coming to the CG meeting.

[binji]

Thanks, @rossberg, I've added an agenda item to the next CG meeting to discuss finding new champions for a handful of these proposals.

[conrad-watt]

Sorry, I didn't realise that clicking and dragging on the list causes the issue to be edited inline. I've deleted my accidental change.

I may as well take this opportunity to say that I'm coming to TPAC and can talk about the threads memory model.

[binji]

Thanks, Conrad. I'll start putting together a schedule this week in TPAC.md.

[titzer]

It would be good to be able to have the exception discussion when people from MTV can dial in. Maybe it fits better on Thursday afternoon?

[chicoxyzzy]

Will it be possible to join online as observer?

[binji]

@titzer OK, I'll move it there for now and we'll see how Thursday progresses.

@chicoxyzzy I haven't seen the room yet so I'm not certain what equipment we'll have available for teleconferencing.

[binji]

@chicoxyzzy We were able to set up the room to use the same zoom.us meeting ID as the WebAssembly CG meeting.

For anyone else who may be reading this, if you are a member of the CG, you can send me an email at binji@google.com and I will send you the meeting ID.

[binji]

Meeting over, thanks to all who presented and attended!