dan sinclair

This change came out of the bindless work, this is required for bindless. The annotations themselves will be optional. They can make auto work better, but if you dont' add...

I'd recommend accepting both for now. Add an entry to the README that the old versions are deprecated and will be removed in ~6 months. All the glslang internal code...

From the GLSL spec, I don't think `true` is defined in the GLSL preprocessor: > * Expressions following #if and #elif are further restricted to expressions operating on literal integer...

That statement would be invalid as the parser is greedy, so it ends up being `(x--) 7`.

Changing the lexing of `--` would be a breaking change as it makes currently valid programs invalid. There doesn't seem to be much benefit in order to make a custom...

Instead of generating indices, could we just do a combination of both? Keep the approach here which moves proposals into `accepted/`, `inactive/` (and should we have a `rejected/`?) but also...

Not sure if I'm mis-understanding some of the above, but you can already define multiple entry points in a single WGSL file can share structures, definitions and var declarations.

Just to note, this is a request for recursive structs, nested structs are already available in WGSL.

See https://www.w3.org/TR/WGSL/#struct-types where it lists the types of a struct member. The last item: `a structure type that has a creation-fixed footprint`. The recursive struct is an error because, currently,...