dan sinclair

> committee has been debating things like adding syntax sugar for features that no compiler toolchain would emit, often completely divorced from any real use case, or feedback from ISVs/users...

We have to get the syntax in to a mostly correct ordering before releasing as we can't really change it afterwards. We're trying to find the minimal things we can...

Even just providing the image with the explanation from the initial discussion bug would be a great improvement since these rules aren't referenced at all in the spec. Yes, the...

I'm going to close this. We still want to make this change, but given it's been 4 months and this CL is trivial it's easier to re-create it when we...

For the `normalize` builtin, this should specify the result of normalizing a vector of length 0 is a indeterminate value.

Awesome, thanks a lot for putting this together. Reading through the MD file a few questions/comments. Listing things as I read through the doc, some of these refer to prior...

For the `GEOMETRY TRIANGLES` should we take something more complex then just vertex values? It seems like it actually takes a vertex and index buffer of a given stride, so,...

For 13 above, after watching more of the rt video, I don't think it's necessarily the best way. Maybe something like the following would be better? ```groovy SHADER_BIND_GROUP gen generation_group...

The changes to the doc look good to me. One note, you can't assume that you'll be able to determine the type of a thing from the name. So `SHADER_GROUP...

I'm guessing we could do this with notify (@willeybryan). Have the form add the user to a notify list, and then hookup something during publishing to send the notify emails?...