You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 22, 2021. It is now read-only.
The next meeting will be Friday, November 13 at 9:00AM - 10:00AM PST/ 6:00PM - 7:00PM CET. Notice that the European time has changed again due to the end of daylight savings time in the US. Please respond with agenda items you would like to discuss.
If this meeting doesn't already appear on your calendar, or you are a new attendee, please fill out this form to attend.
Can we add #395 for discussion for inclusion? Also if time permits --
Can we discuss situations where algorithmic performance is different among different architectures?
I'm pretty sure WASM benefits from an approach that serves the most when possible (the utilitarian approach), but it would be helpful to know if we intend to support CPU detection in any future proposal.
No problem, @penzn! Here are the notes. We'll be skipping the meeting two weeks from now due to Thanksgiving in the US, but we will resume two weeks after that.
The next meeting will be Friday, November 13 at 9:00AM - 10:00AM PST/ 6:00PM - 7:00PM CET. Notice that the European time has changed again due to the end of daylight savings time in the US. Please respond with agenda items you would like to discuss.
If this meeting doesn't already appear on your calendar, or you are a new attendee, please fill out this form to attend.
Carryover items from the last meeting include:
The text was updated successfully, but these errors were encountered: