Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Creating a GC subgroup #80

Closed
binji opened this issue Mar 17, 2020 · 14 comments
Closed

Creating a GC subgroup #80

binji opened this issue Mar 17, 2020 · 14 comments

Comments

@binji
Copy link
Member

binji commented Mar 17, 2020

Given that the meeting to discuss creating a GC subgroup has been postponed a few times now (most recently here), we should probably try to have the discussion asynchronously on a GitHub issue.

The primary things we should do:

  • Plan a time and cadence for regular meetings (see, for example, the simd and interface type meetings). Every two weeks seems like a good default, but feel free to decide as a subgroup
  • Create a charter (see for example the WASI charter)
@fgmccabe
Copy link

I agree.
However, it would be good to float a charter -- to focus the discussion.

@lars-t-hansen
Copy link
Contributor

Indeed. We have people interested in the full reftypes+objects GC proposal but also in linear-memory GC assists (I'm in both factions) and we should at least figure out if we're going to discuss both those things or only the former.

@kripken
Copy link
Member

kripken commented Mar 18, 2020

I'm also in both factions (native GC objects and linear-memory GC assisting). If we think it's too much space to cover in a specific subgroup, perhaps two separate subgroups? However, I think given the overlap that might be less efficient.

@rossberg
Copy link
Member

I tried drafting a charter in #82, stealing properly from the WASI charter. Comments welcome.

@aardappel
Copy link

+1 for both factions ;)

@binji
Copy link
Member Author

binji commented May 8, 2020

We've agreed in the community group to have the subgroup meet, so let's plan for a first meeting in the next month. It seems like generally our groups prefer meetings starting in the range 8am-10am PT (5pm-7pm CET), so I'll assume the same here.

Please fill out this form with your preferences: https://forms.gle/ukXFhz4t3mtMhCG78

@GergelyBuday
Copy link

I am interested. What should I read that was done on GC previously?

@binji
Copy link
Member Author

binji commented May 12, 2020

The best resource to start are the overviews:

From this repo:
https://github.com/WebAssembly/gc/blob/master/proposals/gc/Overview.md
https://github.com/WebAssembly/gc/blob/master/proposals/gc/MVP.md

And a second proposal in a forked repo:
https://github.com/soil-initiative/gc/pull/1
https://github.com/soil-initiative/gc/pull/2

And discussion about a linear-memory GC here:
#78

And finally some discussion on stack-walking to implement a GC here:
WebAssembly/design#1340

@binji
Copy link
Member Author

binji commented May 18, 2020

Thank you to everyone who filled out the form. The times that worked for most people are:

  • Monday, May 18, 9am PDT (6pm CET) 16 votes
  • Tuesday, May 19, 9am PDT (6pm CET) 16 votes
  • Friday, May 29, 9am PDT (6pm CET) 15 votes

My apologies for not posting this sooner, as the Monday time has already past, and tomorrow's meeting is probably too soon for an agenda.

Given that, I suggest we have our first meeting Tuesday, June 2nd, 9am PDT (6pm CET). This meeting time uses the same slot as the larger community group meeting, but on the off week. Most of the group (60%) said they'd prefer a two week cadence, which works well here too.

@binji
Copy link
Member Author

binji commented May 18, 2020

I've added an issue to collect agenda items for the first meeting: #89.

@lars-t-hansen
Copy link
Contributor

9am PDT is 6pm CET at the moment (and on that day).

@kmiller68
Copy link

Is there going to be a calendar invite with the, presumably, zoom details? I didn't add my email to the list until today so it could be I missed the email blast.

@binji
Copy link
Member Author

binji commented May 19, 2020

@lars-t-hansen oops, thanks.
@kmiller68 Yep, I'll set up the calendar event and zoom details this week. I haven't sent anything out yet.

@binji
Copy link
Member Author

binji commented May 27, 2020

We now have a charter and a first meeting scheduled, closing this issue.

@binji binji closed this as completed May 27, 2020
rossberg pushed a commit that referenced this issue Feb 24, 2021
The data count section has a count that must match the number of data segments. If the data count section isn't present, then `memory.init` and `data.drop` cannot be used.

Fixes issue #73.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants