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
Per-process is complicated by the fact that WASI doesn't have a concept of a process, and even if we said that a Wasm instance is a "process", many host implementations run multiple Wasm instances in a single host process, so it's not straightforward to use the host process timer to implement a WASI "instance" timer.
Per-thread is complicated by the fact that when WASI supports threads, some implementations are expected to not have a 1-1 correspondence between WASI threads and host threads, so it's again not straightforward to use the host thread timer to implement a WASI thread timer.
Hello there , Hey I was just wondering ,
Is it still possible for a feature , of one or the other , to build further API's on
for Per-process - OR - per-thread clocks ?
The text was updated successfully, but these errors were encountered: