Re: [w3ctag/design-reviews] SharedArrayBuffer + Atomics (#165)

> We had a brief discussion about SharedArrayBuffer not being transferable, and agree that aspect of the design makes sense. We note that this means that some code that works with ArrayBuffer no longer works with SharedArrayBuffer, but that's probably a good thing since converting code from copying to sharing requires very careful consideration.

To be clear, if you just copy ArrayBuffer now (not transfer), SharedArrayBuffer can easily replace that (except you end up with shared memory, rather than copied memory). If you transfer an ArrayBuffer the original ends up detached, that isn't possible because SharedArrayBuffer doesn't do detachment.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/165#issuecomment-298219067