Michael Shannon

I would also like to raise my hand ✋ in support of this. Due to a large existing codebase (that I cannot change) we have to do the following (all...

@kainino0x Yes, my preference is to use a background worker, though until offscreen canvas is universally supported I may have to proxy calls to the main thread. > We would...

> I think that restriction is important to discourage spin looping behavior. So the problem is when porting code originally written with desktop API's in mind (so really only an...

I just ran into a case where it cannot be known ahead of time whether to call `mapAsync` or `mapSync`. The situation is: 1. `mapAsync` is called, in hopes that...

I just completed an audit of our engine's codebase and there are two use cases where `mapSync` and the other discussions in this issue apply so I thought I would...

I have to 2nd the need for `multiDrawIndirect`. In fact it should be an MVP feature. Without it the amount of draw calls, and thus API/driver overhead, is too great...

I need this feature as well as I have a mono-repo with the following structure: - apps - main-app - packages - library-a - library-b where `main-app` depends on `library-a`...

In an ideal world `precise` (meaning no fusing, reassociation, or distribution) and the other fast math optimizations would be separate. It seems they can be on DX12 and Vulkan, but...

> Do I understand your proposal, @mrshannon ? Yes, just disable fusing, reassociation, and distribution. With signed zeros and such not universal, and the lack of example code that would...

> @mrshannon could you share the intended usage of this attribute? Would you be doing it for the whole module, or potentially more granularly? First, I am specifically talking about...