- From: Domenic Denicola <notifications@github.com>
- Date: Mon, 27 Mar 2023 01:06:23 -0700
- To: whatwg/streams <streams@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Monday, 27 March 2023 08:06:36 UTC
Hmm. I think the idea of `SharedArrayBuffer` was to use the typesystem to encode this sort of guarantee. I.e., if you have a normal `ArrayBuffer`, you know you're safe; if you have a `SharedArrayBuffer`, you're unsafe. What motivates the desire to let the safety vary independently of the type, for this particular web platform feature? Note that wasm memory can be made shraed using `shared: true` in the `WebAssembly.Memory` constructor, and I suspect most wasm thread-using programs already turn that on. -- Reply to this email directly or view it on GitHub: https://github.com/whatwg/streams/issues/757#issuecomment-1484689197 You are receiving this because you are subscribed to this thread. Message ID: <whatwg/streams/issues/757/1484689197@github.com>
Received on Monday, 27 March 2023 08:06:36 UTC