feat(webgpu): use real flags

[MendyBerger]

Resolves #59

[programmerjake]

should there be a separate flag for all or should you just or all the other flags? idk the exact semantics of wit flags, but it seems likely all is intended to be the bitwise-or of all other flags rather than a separate flag

[MendyBerger]

Thanks @programmerjake , great call out!

Let me try to see if I can find any docs why it was added in the first place. Might just be convenience.

In general, we try not to deviate from the WebGPU spec, unless the spec assumes a web feature (e.g. canvas) or a js feature (e.g. function overloading).

[MendyBerger]

Okay, after looking into it, I think it's just a convenience flag for bitwise or-ing all colors.

As I stated above, we try not to deviate from the WebGPU spec unless the spec assumed a web or js feature. I don't think this is such a case, so lets just stick to what the WebGPU working group decided.

And we should document the that these are the only cases when we deviate from the WebGPU spec.

[MendyBerger]

FWIW webgpu.h also kept the all https://github.com/webgpu-native/webgpu-headers/blob/main/webgpu.h#L1334

[programmerjake]

this makes me think flags should support stuff like:

flags gpu-color-write {
    red,
    green,
    blue,
    alpha,
    all = red | green | blue | alpha,
}

that is what the webgpu.h header file does

[MendyBerger]

That would be a nice quality of life change to wit that should be pretty easy implement. Would you open a feature request on https://github.com/WebAssembly/component-model?

[programmerjake]

created WebAssembly/component-model#660