I've been working on this for a while, but haven't filed a tracking issue until now.

The main problem is that ProcessEvents is a polling-based API, so there's no way to get notified/woken when an event happens (like posix poll, or vkWaitForFences). A bunch of other issues also crop up around:

• integration with other OS events (and therefore async runtimes like Tokio, Goroutines, browsers, etc.)
• sync wasm, vs async wasm (jspi/asyncify), vs native, vs native-with-remoting
  • multithreaded usage
  • timing portability
• can only poll all events, and not specific ones

Expect more from me on this soon.

This issue also subsumes:

• Waiting for events without looping: Figure out when callbacks are called, and on what thread #18
• Which threads callbacks get called on: Waiting for asynchronous operations to finish (polling) #91

TODO:

• Add callback modes to the CallbackInfo structs (except UncapturedError)
• A way to get the future for DeviceLost
• ??? Need to go through this issue