Marja Hölttä
Marja Hölttä
Moi Jukka (&others), I'm mostly worrying about this from the "how do we release memory" point of view. In the example in OP, if you never call notify(), the code...
I think there are (at least) 2 separate problems here: 1) The "SAB stays alive" problem can be solved with a suitable indirection object. You could make the closure point...
Ah, I see where I was oversimplifying this :) Thanks for the added info. It might be that coordinating workers wrt "letting the SAB die" (what must die is the...
I don't think WeakRefs would help here. Either the worker has an additional strong pointer to the SAB or not (in addition to the closure ptr which would now be...
In your latest example, if you force a GC, and then try to notify(), will the WeakRef be valid or invalid? I'd guess invalid. If valid, what is keeping the...
The API seems useful (though it's quite subtle why that is :) ). The thought process I used for convincing myself: I wonder whether `Atomics.cancel(sab, index, N)` enables something that's...
And other "Foo constructor"s too, like AggregateError BigInt Boolean Number Symbol %TypedArray% etc etc
cc @syg @sarahghp
This also applies to things like SpeciesCreate resizing the buffer (in TypedArray.prototype functions which use it), or the "array-like" getter resizing the buffer in SetTypedArrayFromArrayLike. Also cc @sarahghp