Skip to content

Latest commit

 

History

History
114 lines (82 loc) · 3.85 KB

CG-12-12.md

File metadata and controls

114 lines (82 loc) · 3.85 KB
Raw

WebAssembly logo

Agenda for the December 12th video call of WebAssembly's Community Group

  • Host: Google Hangouts
  • Dates: Tuesday November 12th, 2017
  • Times: 9:00am–10:00am Pacific Time
  • Location: same Google Hangouts link as before
  • Contact:

Registration

None required if you've attended before. Email JF Bastien to sign up if it's your first time. The meeting is open to CG members only.

Logistics

The meeting will be a Google Hangouts call.

Agenda items

  1. Opening, welcome and roll call
    1. Opening of the meeting
    2. Introduction of attendees
  2. Find volunteers for note taking (acting chair to volunteer)
  3. Adoption of the agenda
  4. Proposals and discussions
    1. Review of action items from prior meeting.
    2. Require custom sections after all known sections (Ben Smith)
  5. Closure

Agenda items for future meetings

None

Schedule constraints

  1. Mozilla people won't be in attendance due to conflict with Mozilla event.

Meeting notes

Roll Call

  • Ben Smith
  • Ben Titzer
  • Brad Nelson
  • Daniel Ehrenberg
  • Derek Schuff
  • Eric Holk
  • Heejin Ahn
  • JF Bastien
  • Jacob Gravelle
  • Keith Miller
  • Michael Ferris
  • Michael Holman
  • Paolo Severini
  • Pat Hickey
  • Richard Winterton
  • Sam Clegg
  • Sergey Rubanov
  • Tomas Nattestad

Opening

Adoption of the agenda

Derek seconds.

Find volunteers for note taking (acting chair to volunteer)

Review of action items from prior meeting.

No meeting until next year.

As voted on last CG video call, the first 2018 meeting will be at APAC friendly time: 9th January, 11PM Pacific Time. This should also be a decept time for Europe folks. If this works well we'll keep every third meeting on that pace.

Discussions

Require custom sections after all known sections

Ben Smith

See WebAssembly/design/issues/1153

We currently can round-trip many things in the text format. One of the things we can’t are custom sections. Not just their order, but their data as well. Similar issue with $ in text format. Talked about having annotation format, but ultimately not really a nice way to say where custom sections should go. Luke suggested we should just have all of them at the end of the file, which everyone does anyways. Technically a breaking change, but we don’t think anyone generates these sections not at the end.

  • Brad: in time I’m worried we’ll use custom sections with hints or something that would be better in the middle. We could experiment with a new type of section this way, and standardize later.
  • Dan: I don’t really see contradiction with banning now, and trying to experiment later.
  • JF: even with evergreen browsers, changing this to allowing only at end, and then back later to anywhere would be tricky. Some binaries would be invalid.
  • Derek: I’m mildly against.
  • Ben Titzer: same here.
  • Ben: how important is it to round-trip? We’re close.
  • Derek: we could specify some ordering in the text format.
  • Eric: how do we do custom sections today?
  • Ben: we don’t.
  • Derek: we could write a counter-proposal.
  • Ben: I have a basic proposal in the github issue. “This custom section goes after this known section”.
  • JF: do we foresee known sections being duplicated?
  • Derek: maybe, with say multiple memories we could do multiple data.
  • Ben: I think it would be worthwhile to not do that.

AI Eric Holk mention “hint” section usecase on github.

AI Ben Smith write counter-proposal on github.

POLL: Should we specify that custom sections must come after all known sections?

Postponed to next meeting.