You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
However, the same Atomics wait operations on the wasm side via memory.atomic.wait32 and memory.atomic.wait64 specify timeout values in nanosecond units:
The functions
Atomics.wait()
andAtomics.waitAsync
use timeout values in millisecond units:However, the same Atomics wait operations on the wasm side via
memory.atomic.wait32
andmemory.atomic.wait64
specify timeout values in nanosecond units:This inconsistency feels a bit odd, so wanted to double check if that was intentional in the spec to utilize the different units?
The text was updated successfully, but these errors were encountered: