dan sinclair
dan sinclair
Related: https://github.com/gpuweb/gpuweb/discussions/3290
I belive it's a typo, yes. In theory it's going to be removed if this issue is fixed, so no reason to fix it at the moment.
I think so.
If the language is confusing, what's the downside in changing it?
There is no built-in way to dump all the buffers in Amber. You'd need to make changes to amber itself in order to copy the buffers back and then write...
From https://gpuweb.github.io/gpuweb/wgsl/#attribute-location: >Must only be applied to an entry point function parameter, entry point return type, or member of a structure type.
Note, that, I believe if it's applied to a `struct` and the struct is passed into the function that _is_ legal. You then ignore the `location`, @dneto0 can you please...
We also need to update what happens with these cases when doing const-eval. `atanh` for instance, it should be a const-eval shader-creation error when calling `atanh` with a value out...
My preference is option 1. Trying to get matching translations in the compilers seems like a lot of work.
Yes, it happens to get handled by the greedy parsing. We could also shift the grammar slightly so it can't happen either way.