Bug 1507112 Comment 4 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

Need a second opinion on this matter from the JS team:
1. JS and Wasm share the same code here, so adding a limit in Wasm will affect JS in some way
2. I cannot find the similar constraint in JS world, e.g. at https://tc39.es/ecma262/#sec-dowait or https://tc39.es/ecma262/#sec-addwaiter -- I guess it is not an issue for instructions/operations reason
3. The current implementation and data structure is not capable to to maintain even a small fraction of 2^32 -- it is linked list.
4. Looks like Atomics.waitAsync is implemented, make this bug an urgent matter (based on the description)

It looks like we need to change the linked list data structure to something like a hashmap or b-tree.
Need a second opinion on this matter from the JS team:
1. JS and Wasm share the same code here, so adding a limit in Wasm will affect JS in some way
2. I cannot find the similar constraint in JS world, e.g. at https://tc39.es/ecma262/#sec-dowait or https://tc39.es/ecma262/#sec-addwaiter -- I guess it is not an issue for instructions/operations reason
3. The current implementation and data structure is not capable to to maintain even a small fraction of 2^32 -- it is linked list.
4. Looks like Atomics.waitAsync is implemented, make this bug an urgent matter (based on the description)

Do we need to change the linked list data structure to something like a hashmap or b-tree?

Back to Bug 1507112 Comment 4