Generated Bindings

[bronter]

Seeing as how there's a >4k line diff to the next version of the wgpu-native headers, I'm starting to look into generating bindings from yaml. The wgpu-native builds now ship with a copy of webgpu.yml, which should cover everything webgpu.h covers, but there are still some thorny issues to get around:

• There isn't (yet) a corresponding wgpu.yml (might be worth making some contributions upstream to resurrect Generate wgpu.h from yaml gfx-rs/wgpu-native#373).
• There would need to be some hard-coded rules for generating certain wrapper code, like making constructor functions for chained structs like SurfaceDescriptor, and merging native extension enums from wgpu.h into their corresponding enums from webgpu.h (since Zig would ordinarily require some messy type casting to use two different enum types for the same field).
• Pointer types from C sometimes don't make as much sense in Zig (for example, Zig has different syntax for many-item vs single-item pointers); the generator needs to be smart enough to generate the appropriate pointer types, and deconstruct/reconstruct array types from pointer and length components when generating bindings for certain methods.
• There are certain unimplemented methods, and I already haven't done the best job of marking them as such, but the generated bindings should do better and either mark them as unimplemented or leave them out. Not really sure how I'll keep the list up-to-date other than manually copying them over from https://github.com/gfx-rs/wgpu-native/blob/trunk/src/unimplemented.rs
• I don't particularly want to shove all the bindings into one file like some bindings generators do; having everything in one file makes it difficult to see what has changed from one version to the next (the problem I've been dealing with on each version update with when it comes to webgpu.h/wgpu.h). The generator should have some rules it uses to separate things out into files and generate imports/exports as needed.

Hopefully soon I'll have some time to look into it further and spin off some issues. It'll probably be a gradual process of getting the generated bindings 1:1 with the manually-written bindings before switching over completely.

[bronter]

I've started work on this, I've got a build step that will run the bindings generator once it's finished. Right now the issue I'm facing is that webgpu.yml is formatted in a way that breaks any of the YAML parsers for Zig I've tried. So I think I'll probably have to use one of the spec-compliant ones written in C and just work it into the build system.

[hollinwilkins]

If you've got a branch up somewhere I can help take a look potentially.

[spencrc]

Any update on this? I would love to help out if a branch or repository was made public