-
Notifications
You must be signed in to change notification settings - Fork 73
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
Comments
I agree. |
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. |
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. |
I tried drafting a charter in #82, stealing properly from the WASI charter. Comments welcome. |
+1 for both factions ;) |
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 |
I am interested. What should I read that was done on GC previously? |
The best resource to start are the overviews: From this repo: And a second proposal in a forked repo: And discussion about a linear-memory GC here: And finally some discussion on stack-walking to implement a GC here: |
Thank you to everyone who filled out the form. The times that worked for most people are:
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. |
I've added an issue to collect agenda items for the first meeting: #89. |
9am PDT is 6pm CET at the moment (and on that day). |
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. |
@lars-t-hansen oops, thanks. |
We now have a charter and a first meeting scheduled, closing this issue. |
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.
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:
The text was updated successfully, but these errors were encountered: