Skip to content

Agenda for subgroup meeting - September 8, 2020 #126

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

Closed
binji opened this issue Aug 25, 2020 · 16 comments
Closed

Agenda for subgroup meeting - September 8, 2020 #126

binji opened this issue Aug 25, 2020 · 16 comments

Comments

@binji
Copy link
Member

binji commented Aug 25, 2020

The next subgroup meeting is Spetember 8, 2020 at 9am PDT (6pm CET). As with other Wasm meetings, we'll host this on zoom.

No registration required if you attended a previous meeting. Fill out the form here if it's your first time: https://forms.gle/JehrAB4gWbtHjybt9.

Please respond to this issue with topics for the agenda.

Agenda:

@RossTate
Copy link
Contributor

I think we should discuss #119. It provides a simple approach to addressing many of the standing problems. It also serves as a good follow-on to last meeting's presentation because it executes upon the some of the takeaways from the presentation.

@rossberg
Copy link
Member

Just a heads-up that I will be off the grid for the next two weeks, so won't be able to attend the next meeting.

@RossTate
Copy link
Contributor

Oh okay, then I think it would be poor form to discuss #119. Given that, since we didn't have time for Q&A and discussion of last meeting's presentation, maybe setting aside some time for that would be useful for the group.

@binji
Copy link
Member Author

binji commented Aug 27, 2020

Given that, since we didn't have time for Q&A and discussion of last meeting's presentation, maybe setting aside some time for that would be useful for the group.

That sounds OK to me, though I'm not sure we'll fill an hour with discussion on this topic, and I'd like to avoid holding a meeting that only has enough content for a half-hour or less. Perhaps we can defer the discussion to the next meeting unless we get another agenda topic?

@RossTate
Copy link
Contributor

Sounds like a good plan to me. I agree that we shouldn't plan for an hour of discussion. Half an hour is the most I would expect, and I'm not sure even that. So it makes sense to schedule based on what other agenda items come up, if any.

@bvibber
Copy link

bvibber commented Aug 27, 2020

It may be too early to have a discussion on it but I'd love as a potential language implementor to have a better understanding of potential behavior on allocation failure cases with respect to heap or object size limits (#122).

@fgmccabe
Copy link

I would like to put the requirements on the agenda. There will have been enough time by then for people to have read the proposed doc.

@RossTate
Copy link
Contributor

I'm happy to have Q&A time be brief to make more room for other items. If we put it first and it ends early, then that'd give even more time.

@binji
Copy link
Member Author

binji commented Aug 28, 2020

OK, I've added these to the agenda. @Brion @fgmccabe @RossTate can you give timebox estimates for these discussions?

@bvibber
Copy link

bvibber commented Aug 28, 2020

Limits & failure cases is probably pretty short if there's general agreement on how to proceed with failing allocations for the MVP. Does 10-ish minutes sound reasonable? I imagine if there are questions we can't resolve quickly with general agreement they'll be pushed back for later offline discussion.

@RossTate
Copy link
Contributor

I imagine the requirements discussion will benefit from a lot of time, so I would put my discussion down for just 10 minutes. I would even suggest putting it before the requirements discussion so that, if it turns out that many have the questions have already been answered through offline discussions, then we can hand off the resulting extra time to the requirements discussion.

@dbezhetskov
Copy link

Hi, I want to attend these meeting and I filled up the form but haven't got any invitation yet.
cc: @littledan

@bvibber
Copy link

bvibber commented Sep 8, 2020

I also submitted the form a few days ago and haven't received an invite.

@binji
Copy link
Member Author

binji commented Sep 8, 2020

Sorry about that, I've added you to the meeting. Let me know if you don't get the email.

@bvibber
Copy link

bvibber commented Sep 8, 2020

Thanks, got it! :)

@binji
Copy link
Member Author

binji commented Sep 8, 2020

Notes for meeting here: WebAssembly/meetings#635

Thanks, everyone!

@binji binji closed this as completed Sep 8, 2020
rossberg added a commit that referenced this issue Feb 24, 2021
* [interpreter] Simplify zero-len and drop semantics

* Update overview

* [spec] Change drop semantics

* [spec] Forgot to adjust prose for *.init ops

* [test] Update generated tests for OOBs and dropping changes (#131)
rossberg pushed a commit that referenced this issue Feb 24, 2021
After the spec change in #126, byte copying order is not observable.
rossberg pushed a commit that referenced this issue Feb 24, 2021
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

6 participants