proposal-ecmascript-sharedmem
proposal-ecmascript-sharedmem copied to clipboard
tc39
Shared memory and atomics for ECMAscript
My understanding is that several browsers have implemented or are implementing Web GL 2.0. Additionally, I would have to assume that the editors do not accept changes to Web GL...
In an aside in Issue #1, @jfbastien writes: "How does SAB affect the web API surface area? Most APIs weren't designed to be called from multiple threads, and have led...
I'd like a section, maybe `PERFORMANCE.md` or in `DISCUSSION.md`, which explains the performance goals of this spec, and open areas which can help bridge the gap with native. It'll be...
As discussed in #88, it is desirable to have a formal memory model for SharedArrayBuffer. We've secured funding for such a project, and will be pursuing it over the next...
**TL;DR**: IMO getting formal memory model work _started_ (not necessarily _finished_) should block moving the spec to [Stage 3](https://tc39.github.io/process-document/). I like SAB, but I don't trust English when we could...
@pizlonator, @jfbastien, @ogiroux With the demise of the synchronic proposal (Issue #12) we're back to futexes as the main blocking mechanism. From that comes some further issues we should discuss:...
(An idea that's been floating around for a while, recorded for posterity, not really urging its adoption yet.) At present the spec allows `futexWait()` to throw if an agent does...